[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] ImageMagick Support on Windows

From: Eli Zaretskii
Subject: Re: [Emacs-diffs] ImageMagick Support on Windows
Date: Wed, 15 Oct 2014 13:35:23 +0300

> From: address@hidden
> Cc: address@hidden
> Date: Wed, 15 Oct 2014 18:38:30 +0900
> In my case, crashed at imagemagick-types in image.c.
> imagemagick-register-types is called in image.el and finally
> imagemagick-types in image.c is called, but at this time, imagemagick
> functions are not initialized yet. then temacs crash.
> I add init_imagemagick_functons to imagemagick-types.

I think that's the right fix, thanks.

> And, for imagemagick-register-types to work well, there was a need to
> load image.el after w32-win.el in loadup.el because
> dynamic-library-alist is set in w32-win.el.

That's probably correct as well.

> Yes, libMagickWand-XXX.dll depend on libMagickCore-XXX.dll and
> libMagickCore-XXX.dll is automatically loaded when load
> libMagickWand-XXX.dll.
> But some functions used in image.c is in libMagickCore-XXX.dll.
> To get these functions by GetProcAddress, need to load
> libMagickCore-XXX.dll separately.
> Although is not a smart way, I add two DLLs as below
> to dynamic-library-alist and load each library separately.
> (My imagemagick is built without --enable-hdri.)
> '(magickwand "libMagickWand-6.Q16-2.dll")
> '(magickcore "libMagickCore-6.Q16-2.dll")

Yuck!  I think it's much better to teach w32-win.el and
w32_delayed_load to load more than one library for a certain image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]