Re: SVG to PNG

>>
>> However, I was expecting to have something like
>> #define MagickLibConfigPath "./config/"
>> ?!?
>>
> It may be that some unneeded pre-processor definitions remain.
For me this is rather a bug.

>>
>> So, there is no Linux dependent types defined? I thought Solaris would be
>> the equivalent for linuxish systems ?
>>
>Nope.
This, if not a bug, is not a sufficient solution, not to be able to
differentiate type.mgk based on OS, especially Linux. Font substitution
should be possible based on OS. I could patch it of course, but I would
appreciate seeing the GM even better.
For the me one solution could be something like in *type.c*

/*

  Define declarations.

*/

#ifdef WIN32

#define TypeFilename  "type.mgk"

#endif


#ifdef unix

#define TypeFilename  "type-linux.mgk"

#endif



Am Fr., 20. Nov. 2020 um 09:15 Uhr schrieb Pro Turm <[email protected]>:

> > If you execute the program with the environment variable
> MAGICK_DEBUG=configure as suggested before
> As I tried to explain, I don't use the binary GM, neither do I want to
> compile it to a binary. I'm trying to integrate the gm sources into my
> application.
>
> Am Do., 19. Nov. 2020 um 15:23 Uhr schrieb Bob Friesenhahn <
> [email protected]>:
>
>> On Thu, 19 Nov 2020, Pro Turm wrote:
>> >
>> > However, I was expecting to have something like
>> > #define MagickLibConfigPath "./config/"
>> > ?!?
>>
>> It may be that some unneeded pre-processor definitions remain.
>>
>> All of the configuration work is done in the InitializeMagickEx()
>> function, which includes this hunk of code:
>>
>>    /*
>>      Establish the path, filename, and display name of the client app
>>    */
>>    InitializeMagickClientPathAndName(path);
>>    /*
>>      If the client name did not get setup for any reason, we take one
>>      last shot at it using the data the caller passed us.
>>    */
>>    if (GetClientName() == (const char *) NULL)
>>      DefineClientName(path);
>>
>> If you execute the program with the environment variable
>> MAGICK_DEBUG=configure as suggested before, then all the steps being
>> done will be made clear.  The most important thing is to discover
>> where the program's files are installed.  Then the paths to other
>> installation components are computed based on that location.
>>
>> After building the software under Linux, you do need to install it
>> somewhere for testing.  You can use the DESTDIR environment variable
>> to influcence where the files are installed to.
>>
>> For example
>>
>>    mkdir $HOME/install
>>
>>    DESTDIR=$HOME/install make install
>>
>> and now the GraphicsMagick installation should be located under
>> $HOME/install, and when using --disable-installed, it should still
>> work, even if you later move that directory.
>>
>> After installation, we can successfully do this:
>>
>>    $HOME/install/usr/local/bin/gm -version
>>
>> The "/usr/local" part is just an artifact caused by the default prefix
>> and you can remove it.  The configure option --prefix='/' makes the
>> installation footprint look nicer:
>>
>>    $HOME/install/bin/gm -version
>>
>> Bob
>> --
>> Bob Friesenhahn
>> [email protected],
>> http://www.simplesystems.org/users/bfriesen/
>> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
>> Public Key,
>> http://www.simplesystems.org/users/bfriesen/public-key.txt
>>
>>
>> _______________________________________________
>> Graphicsmagick-help mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/graphicsmagick-help
>>
>

_______________________________________________
Graphicsmagick-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/graphicsmagick-help