From: Claudio Bley <claudio.bley@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH 0/5] [RFC] fixes for w32 and NetPBM
Date: Tue, 29 Oct 2013 08:02:27 +0100 [thread overview]
Message-ID: <87mwlsv9to.wl%claudio.bley@gmail.com> (raw)
In-Reply-To: <838uxhgpfk.fsf@gnu.org>
At Fri, 25 Oct 2013 21:45:19 +0300,
Eli Zaretskii wrote:
>
> > From: claudio.bley@gmail.com (Claudio Bley)
> > Date: Fri, 25 Oct 2013 17:35:18 +0200
> >
> > Here are a few patches that have piled up in my local branch over the
> > last few months.
>
> Thanks.
>
> > w32: define new jpeglib-version var in order to load the correct DLL
> > at runtime
>
> Are the newer DLLs binary incompatible with the older ones? If not,
> I'd prefer not to introduce any version checking, since this increases
> the probability of the user's DLL being rejected by Emacs for no good
> reason.
Yes, it seems all releases since version 7 are incompatible with the
former ones.
> If there are indeed incompatibilities, can you point to the
> documentation that describes them?
I don't have a link to official documentation at hand (the jpeglib
website is a bit sparse), so I'm quoting wikipedia
(https://en.wikipedia.org/wiki/Jpeglib):
,----
| There are currently two conditions which trigger a major version bump
| of the JPEG library:
|
| 1. New types of files can be created which are not compatible with prior releases, and
| 2. Changes in the master records which break the binary compatibility (usually addition of entries for new functions).
|
| In all major upgrades since v6 both conditions 1. and 2. came
| together, while the source compatibility (API) could largely be
| retained.
`----
> > w32: add support for default library names for libtiff
>
> Where did you find these newer ports of libtiff? Maybe we should
> amend the instructions in nt/INSTALL and nt/README.W32.
I'm using the latest officially released version from
http://www.remotesensing.org/libtiff/.
> > Fix file magic for pbm files with comments
>
> I don't think I've seen this part. Did you send it?
Somehow this part didn't make it. I'll re-send.
next prev parent reply other threads:[~2013-10-29 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:35 [PATCH 0/5] [RFC] fixes for w32 and NetPBM Claudio Bley
2013-10-25 18:45 ` Eli Zaretskii
2013-10-29 7:02 ` Claudio Bley [this message]
2013-11-01 9:32 ` Claudio Bley
2013-11-01 9:49 ` Eli Zaretskii
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=87mwlsv9to.wl%claudio.bley@gmail.com \
--to=claudio.bley@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).