all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christoph <cschol2112@googlemail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: imagemagick support on W32
Date: Fri, 01 Oct 2010 06:04:08 -0600	[thread overview]
Message-ID: <4CA5CE38.9010807@gmail.com> (raw)
In-Reply-To: <AANLkTim15SapxmGkE7VNPDWyDLRS2p-B0AiEqXsnWiiz@mail.gmail.com>

On 10/1/2010 4:37 AM, Juanma Barranquero wrote:

> In theory, you could statically link any library to Emacs, but IMO in
> this case is much better to stick to using the DLLs. The library is
> big, unneeded when you start with -nw or in -batch mode, and it's
> easier to update as DLLs than recompiling/relinking Emacs (which the
> common, non-developer user cannot do).

That makes much sense.

> It shouldn't be difficult, but there are a few tricky details, I
> think. If ImageMagick is loaded,
> image-library-alist/init-image-library will have to act as if every
> image type supported by ImageMagick is loaded (or there is a way to
> ask ImageMagick for a list of the formats it support?) But even if
> Emacs is compiled with ImageMagick support, a given instance could be
> unable to load the libraries (not found in the path, or whatever), and
> in this case, the other libraries could be loaded. Assuming, of
> course, that compiling with ImageMagick support does not deactivate
> (at compile time) the other image libraries' stuff. Does it?

I guess Joakim answered this in his email. I will have a look at at 
that. Thanks.

> Eli's question is very relevant. I had trouble in the past mixing
> MSVC-compiled Emacs and MinGW-compiled image libraries; perhaps you're
> seeing just the opposite. Both runtimes are not compatible; in fact,
> if the library uses stdio facilities to access files you'll get all
> kind of havoc. It'd be easier if you can compile ImageMagick with
> MinGW.

I will answer Eli's question here. AFAIK, the libraries from 
ImageMagick's website are compiled with MSVC. I had read somewhere that 
MSVC/mingw libraries are mostly incompatible but figured I'd give it 
shot anyway, since my original problem was Emacs not finding the 
libraries during linking.

Now, I have tried compiling ImageMagick with mingw but that turned out 
to be a huge pita. I installed all necessary GnuWin32 libs, and even 
MSYS, and ./configure would fail with lots of problems still. It says it 
can't find some components of the different packages (jpeg, png etc.) 
and basically disabled the support for those. I do have all the GnuWin32 
dev packages installed and it finds most of the headers.

Sounds like I will have to sort that out after all and get some mingw 
dll's compiled first before going on.

Thanks,
Christoph



  parent reply	other threads:[~2010-10-01 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  1:44 imagemagick support on W32 Christoph
2010-10-01  1:52 ` Juanma Barranquero
2010-10-01  2:27   ` Christoph
2010-10-01  2:32     ` Christoph
2010-10-01  2:58       ` Christoph
2010-10-01  3:16         ` Juanma Barranquero
2010-10-01  4:16           ` Christoph
2010-10-01  7:30             ` Eli Zaretskii
2010-10-01 10:37             ` Juanma Barranquero
2010-10-01 11:36               ` joakim
2010-10-01 12:12                 ` Christoph
2010-10-01 12:38                   ` joakim
2010-10-01 19:57                     ` Juanma Barranquero
2010-10-01 20:41                       ` joakim
2010-10-02  3:31                     ` Jason Rumney
2010-10-01 19:51                 ` Juanma Barranquero
2010-10-01 20:44                   ` joakim
2010-10-01 20:53                     ` Juanma Barranquero
2010-10-01 12:04               ` Christoph [this message]
2010-10-01 19:55                 ` Juanma Barranquero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA5CE38.9010807@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.