all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Revision 110444 breaks the native MS-Windows build
Date: Mon, 08 Oct 2012 03:20:12 -0700	[thread overview]
Message-ID: <5072A8DC.6010208@dancol.org> (raw)
In-Reply-To: <83wqz149ot.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 3187 bytes --]

On 10/8/2012 2:03 AM, Eli Zaretskii wrote:
>   #if defined (HAVE_NTGUI) && !defined (WINDOWSNT)

Thanks.

> and in jconfig.h, a jpeglib header included by jpeglib.h, I see this:
> 
>   #ifdef _WIN32
>   # include <windows.h>
>   /* Define "boolean" as unsigned char, not int, per Windows custom */
>   # if !defined __RPCNDR_H__ || defined __MINGW32__    /* don't conflict if rpcndr.h already read */
>   #  ifndef boolean     /* don't conflict if rpcndr.h already read */
>       typedef unsigned char boolean;
>   #  endif /* boolean */
>   # endif /* __RPCNDR_H__ */
>   # define HAVE_BOOLEAN     /* prevent jmorecfg.h from redefining it */
>   # define USE_WINDOWS_MESSAGEBOX 1
>   #endif /* _WIN32 */
> 
> This seems to be in perfect order, so I don't understand the conflict
> you were seeing.
> 
> In any case, you cannot hope for the above to compile unless you also
> typedef jpeg_boolean.

My jpeglib doesn't have that code.  The redefinition actually works fine under
Cygwin --- the jpeglib headers there just define a type they call "boolean",
which, thanks to our preprocessor macro, is substituted with jpeg_boolean.
Presumably, my hack breaks native Windows because there jpeglib _doesn't_ define
boolean.

I tried replacing my hack with the approach below. It does _not_ work ---
although this patch allows Emacs to compile under both Cygwin and native
Windows, it doesn't result in successful JPEG loading under Cygwin, presumably
due to the ABI we've made the jpeglib headers declare no longer matching the
compiled libjpeg we're using.

+/* rpcndr.h and jpeglib.h both define boolean types.  In certain
+   configurations, jpeglib won't detect that rpcndr.h has already
+   defined a boolean type and will instead try to define its own
+   conflicting type.
+
+   At this point, we know we've included windows.h and with it
+   rpcndr.h.  First, include the jpeglib configuration file: if
+   jpeglib thinks the system doesn't have a boolean type, correct this
+   misconception before including the rest of jpeglib.
+
+   */
+#include <jconfig.h>
+#ifndef HAVE_BOOLEAN
+#define HAVE_BOOLEAN 1
+#endif
 #include <jpeglib.h>
 #include <jerror.h>

Instead, let's do this:

+/* rpcndr.h (via windows.h) and jpeglib.h both define boolean types.
+   Some versions of jpeglib try to detect whether rpcndr.h is loaded,
+   using the Windows boolean type instead of the jpeglib boolean type
+   if so.  Cygwin jpeglib, however, doesn't try to detect whether its
+   headers are included along with windows.h, so under Cygwin, jpeglib
+   attempts to define a conflicting boolean type.  Worse, forcing
+   Cygwin jpeglib headers to use the Windows boolean type doesn't work
+   because it created an ABI incompatibility between the
+   already-compiled jpeg library and the header interface definition.
+
+   The best we can do is to define jpeglib's boolean type to a
+   different name.  This name, jpeg_boolean, remains in effect through
+   the rest of image.c.
+*/
+#if defined (CYGWIN) && defined (HAVE_NTGUI)
 #define boolean jpeg_boolean
+#endif
 #include <jpeglib.h>
 #include <jerror.h>



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  parent reply	other threads:[~2012-10-08 10:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08  8:38 Revision 110444 breaks the native MS-Windows build Eli Zaretskii
2012-10-08  8:40 ` Daniel Colascione
2012-10-08  9:03   ` Eli Zaretskii
2012-10-08  9:20     ` Eli Zaretskii
2012-10-08 10:20     ` Daniel Colascione [this message]
2012-10-08 11:56       ` 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

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

  git send-email \
    --in-reply-to=5072A8DC.6010208@dancol.org \
    --to=dancol@dancol.org \
    --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 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.