From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Newsgroups: gmane.emacs.devel Subject: Re: imagemagick support on W32 Date: Fri, 01 Oct 2010 06:04:08 -0600 Message-ID: <4CA5CE38.9010807@gmail.com> References: <4CA53CE5.1020702@gmail.com> <4CA54727.6010900@gmail.com> <4CA54834.4020106@gmail.com> <4CA54E67.5040703@gmail.com> <4CA560A0.50901@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1285934773 11642 80.91.229.12 (1 Oct 2010 12:06:13 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Oct 2010 12:06:13 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 01 14:06:12 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P1eNP-0000OQ-JR for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 14:06:11 +0200 Original-Received: from localhost ([127.0.0.1]:59611 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1eNO-0008Mq-Ib for ged-emacs-devel@m.gmane.org; Fri, 01 Oct 2010 08:06:10 -0400 Original-Received: from [140.186.70.92] (port=40656 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1eLX-0007rJ-3C for emacs-devel@gnu.org; Fri, 01 Oct 2010 08:04:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1eLV-0004aI-PY for emacs-devel@gnu.org; Fri, 01 Oct 2010 08:04:15 -0400 Original-Received: from mail-qw0-f41.google.com ([209.85.216.41]:48754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1eLV-0004Zz-Lq; Fri, 01 Oct 2010 08:04:13 -0400 Original-Received: by qwb8 with SMTP id 8so1241427qwb.0 for ; Fri, 01 Oct 2010 05:04:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ly5vCYvSGuQVBh7lggK9NwyZo267Rc6eKISJCnLFAXo=; b=BhG8q+i80MsoI3WdzC0xsnEJZJ98jdVOiH06W5zo56/3Wdw1XnlY9PFyMSKzyFgpA6 1NIknDAz/HzAlmEsFpZzU+FgvGK7Fa86nWESieaNViwA8Hmywhyjwnu83HcI7s/u86Wh +0VJT3kKhwwpVW9rrO5DAd1RH/1Z9caqxtu58= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Qp85ZRpEYvdRYgjTjinkbZAaWVR4RzUufvL/dCDs9+jkWXfvMLr9D5dswLtKq2XmQ4 yfvr2V4y88Im5Iqs4JuWH4gHzABD9R+knMb7DKY2YuCjVYBhQ4j9oOU+nhGx23YPQRIO Ov8z6hrb4DL9wFFo/Ez/Jb2SVKx8lZ9ARY1Ak= Original-Received: by 10.224.114.163 with SMTP id e35mr3736995qaq.140.1285934651677; Fri, 01 Oct 2010 05:04:11 -0700 (PDT) Original-Received: from [192.168.1.5] (67-41-203-171.hlrn.qwest.net [67.41.203.171]) by mx.google.com with ESMTPS id t18sm1186188qco.8.2010.10.01.05.04.09 (version=SSLv3 cipher=RC4-MD5); Fri, 01 Oct 2010 05:04:10 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:131152 Archived-At: 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