This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [64bit] type conflict for INT32
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 12 Apr 2013 17:07:29 +0200
- Subject: Re: [64bit] type conflict for INT32
- References: <5166EB44 dot 6010907 at cornell dot edu> <51673471 dot 3060401 at users dot sourceforge dot net> <5168145F dot 1 at cwilson dot fastmail dot fm> <51681928 dot 2050708 at cornell dot edu>
- Reply-to: cygwin-apps at cygwin dot com
On Apr 12 10:24, Ken Brown wrote:
> On 4/12/2013 10:04 AM, Charles Wilson wrote:
> >On 4/11/2013 6:08 PM, Yaakov (Cygwin/X) wrote:
> >>It does mean that Win32API (or X11, for that matter) headers must be
> >>#include'd before <jpeglib.h>. Before I spin a new release, could you
> >>test if this works with emacs?
> >
> >Would this problem go away if we switched to jpeg-turbo?
>
> No, the 64bit repository is already using jpeg-turbo.
And, in fact, it's not *really* a terrible problem, is it? You have to
expect type name conflicts when mixing applications and libraries from
the POSIX world with Windows headers. Just see the stuff in the newlib,
Cygwin, and w32api headers centered around conflicting definitions due
to winsock being almost, but not quite, BSD sockets.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat