Re: GM in one binary

Bob Friesenhahn <[email protected]>
Newsgroups gmane.comp.video.graphicsmagick.help
Message-ID <[email protected]>
On Wed, 13 Jun 2018, Artsimovich, Wladislav wrote:

>> the default "delegates" configuration is essentially empty
> I guess I noticed that already. I compiled GM with MinGW64, without setting ENV Paths and executing
> errored out with "Unable to access configuration file (delegates.mgk)."

An actual error (maybe only a warning?) is not good.

Given what you appear to be doing (and now that I know you are using 
MinGW64 with configure), I suggest you add --disable-installed to your 
configure options:

   --disable-installed     disable building an installed GraphicsMagick

This option removes hard-coded search paths for files and builds 
relative paths instead.

Set MAGICK_DEBUG=configure in the environment if you need to debug 
initialization issues.  This should cause logging of what GM is doing 
while it is initializing.

>> I don't think that there is a compile option which keeps the software
>> from looking for the external ".mgk" files. The external ".mgk" files
>> are loaded via a function called GetConfigureBlob() in magick/blob.c
>> so it is easily modified if need be.
> Easily is a relative term ;D
> Delving into C code is really intimidating for a C virgin, especially with all the #if defineds. So basically:
> Step1: Figure out how to prevent GetConfigureBlob() from searching
> Step2: Figure out how the .mgk files work and populate them to work when statically linked
> Step3: Link dependencies and GM into one binary
> And it should work, correct?

Hopefully it is not too hard. :-)

If you need minor improvements we can get them into the next release.

Bob

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.