From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: ofv@wanadoo.es, lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: 64-bit build on Windows
Date: Mon, 23 Jan 2017 05:30:38 +0200 [thread overview]
Message-ID: <83efzu4fmp.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9O9ijH1nPDbBd3iVa=th1V1cOtzvdf6fXKedR4tFVF68Q@mail.gmail.com> (message from Fabrice Popineau on Sun, 22 Jan 2017 21:38:39 +0100)
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Sun, 22 Jan 2017 21:38:39 +0100
> Cc: Juanma Barranquero <lekktu@gmail.com>, Óscar Fuentes <ofv@wanadoo.es>,
> Emacs developers <emacs-devel@gnu.org>
>
> > + '(magickwand "libMagickWand-7.Q16HDRI-0.dll" "libMagickWand-7.Q16-0.dll")
> > + '(magickcore "libMagickCore-7.Q16HDRI-0.dll" "libMagickCore-7.Q16-0.dll")
>
> Does this mean we will only support ImageMagick 7.x and later on
> Windows? If so, the configure-time test should be changed, since it
> currently allows 6.x, I think.
>
> Given that MSYS2 itself has switched to IM7, I don't see the point to keep support forIM6.
But ImageMagick libraries were available as DLLs regardless of what
MSYS2 did or didn't do, so I think we should have associations for
those binaries as well, for ImageMagick 6.x.
> > @@ -8406,7 +8776,7 @@ imagemagick_compute_animated_image (MagickWand *super_wand, int
> ino)
> > PixelWand **source, **dest;
> > size_t source_width, source_height;
> > ssize_t source_left, source_top;
> > - MagickPixelPacket pixel;
> > + PixelInfo pixel;
>
> What is this about?
>
> AFAIR they changed the names of a few structures.
Then this should be conditioned on ImageMagick version, and we
probably need a Lisp variable holding the version number to look for
DLLs that are specific to the version against which Emacs was
compiled, similar to libpng-version.
next prev parent reply other threads:[~2017-01-23 3:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 1:40 64-bit build on Windows Juanma Barranquero
2017-01-20 8:06 ` Eli Zaretskii
2017-01-21 18:29 ` Juanma Barranquero
2017-01-21 18:38 ` Eli Zaretskii
2017-01-20 13:42 ` Phillip Lord
2017-01-20 14:32 ` Óscar Fuentes
2017-01-20 15:54 ` Eli Zaretskii
2017-01-20 19:51 ` Fabrice Popineau
2017-01-21 18:25 ` Eli Zaretskii
2017-01-21 19:04 ` Fabrice Popineau
2017-01-21 19:15 ` Juanma Barranquero
2017-01-21 19:23 ` Fabrice Popineau
2017-01-21 19:30 ` Juanma Barranquero
2017-01-21 19:55 ` Eli Zaretskii
2017-01-21 20:40 ` Fabrice Popineau
2017-01-22 16:50 ` Eli Zaretskii
2017-01-22 20:38 ` Fabrice Popineau
2017-01-22 21:22 ` Paul Eggert
2017-01-22 21:39 ` Fabrice Popineau
2017-01-23 3:37 ` Eli Zaretskii
2017-01-23 3:30 ` Eli Zaretskii [this message]
2017-01-21 18:57 ` Juanma Barranquero
2017-01-21 19:52 ` Eli Zaretskii
2017-01-21 21:15 ` Juanma Barranquero
2017-01-21 21:42 ` Juanma Barranquero
2017-01-21 22:30 ` Nikolay Kudryavtsev
2017-01-21 22:43 ` Óscar Fuentes
2017-01-22 3:38 ` Eli Zaretskii
2017-01-21 21:18 ` Juanma Barranquero
2017-01-22 17:50 ` Stephen Leake
2017-01-22 18:07 ` Eli Zaretskii
2017-01-22 20:30 ` Fabrice Popineau
2017-01-21 18:37 ` Juanma Barranquero
2017-01-26 19:05 ` Arash Esbati
2017-01-27 6:07 ` Fabrice Popineau
-- strict thread matches above, loose matches on Subject: below --
2017-01-21 23:12 Angelo Graziosi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efzu4fmp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@gmail.com \
--cc=lekktu@gmail.com \
--cc=ofv@wanadoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).