All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
	Roy Tam <roytam@gmail.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] fix MinGW compilation when --enable-vnc-jpeg is specified
Date: Thu, 23 Jun 2011 17:05:46 +0200	[thread overview]
Message-ID: <4E03564A.5060201@mail.berlios.de> (raw)
In-Reply-To: <20110623135202.GA12765@stefanha-thinkpad.localdomain>

Am 23.06.2011 15:52, schrieb Stefan Hajnoczi:
> On Sat, Jun 18, 2011 at 10:35:57AM +0200, Stefan Weil wrote:
>> Am 18.06.2011 07:13, schrieb Roy Tam:
>>> This patch fix conflicting types for 'INT32' in basetsd.h in including
>>> qemu-common.h first.
>>>
>>>
>>> Sign-off-by: Roy Tam<roytam@gmail.com>
>>> --
>>> diff --git a/ui/vnc-enc-tight.c b/ui/vnc-enc-tight.c
>>> index 87fdf35..1591df0 100644
>>> --- a/ui/vnc-enc-tight.c
>>> +++ b/ui/vnc-enc-tight.c
>>> @@ -28,6 +28,8 @@
>>>
>>> #include "config-host.h"
>>>
>>> +#include "qemu-common.h"
>>> +
>>> #ifdef CONFIG_VNC_PNG
>>> #include<png.h>
>>> #endif
>>> @@ -36,8 +38,6 @@
>>> #include<jpeglib.h>
>>> #endif
>>>
>>> -#include "qemu-common.h"
>>> -
>>> #include "bswap.h"
>>> #include "qint.h"
>>> #include "vnc.h"
>>
>> Acked-by: Stefan Weil <weil@mail.berlios.de>
>>
>> The conflicting declaration is in jmorecfg.h which is included from
>> jpeglib.h.
>
> Is the problem that the Windows headers included from qemu-common.h try
> to #define INT32?
> http://msdn.microsoft.com/en-us/library/aa383751(v=vs.85).aspx
>
> In that case I think an explicit fix is better:
>
> #ifdef _WIN32
> /* Include this before jpeglib.h for the INT32 definition */
> #include <basetsd.h>
> #endif
>
> ...followed by png/jpeg includes...
>
> Simply moving qemu-common.h provides no hints and is rather indirect.
> Someone may move it back in the future.
>
> Stefan

INT32 is declared in basetsd.h which is included from windows.h
(with some indirections) which is included from qemu-os-win32.h
which is included from qemu-common.h.

INT32 is not a #define, but a data type (typedef) and very common
for w32 compilations. Windows programmers don't include basetsd.h
directly, but usually use windows.h.

Including qemu-common.h right at the beginning (after config.h where
needed) should be good practice for QEMU source code - like this:

#include "config.h"        /* optional */
#include "qemu-common.h"
#include <system includes> /* without those that are included from 
qemu-common.h */
...
#include "other local includes"
...

As long as the maintainers don't accept patches which simply move
qemu-common.h, there is no danger. :-)

Of course a comment might be added. In most cases, I'm a great friend
of good comments, but in this special case, I don't think it is necessary.
It's a very special case of a typedef conflict caused by the mingw32
version of jpeglib (which is obviously rarely used), and it might be fixed
in a newer version of jpeglib (so the comment would be no longer
valid, and nobody would notice that).

Stefan



WARNING: multiple messages have this Message-ID (diff)
From: Stefan Weil <weil@mail.berlios.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
	Roy Tam <roytam@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] fix MinGW compilation when --enable-vnc-jpeg is specified
Date: Thu, 23 Jun 2011 17:05:46 +0200	[thread overview]
Message-ID: <4E03564A.5060201@mail.berlios.de> (raw)
In-Reply-To: <20110623135202.GA12765@stefanha-thinkpad.localdomain>

Am 23.06.2011 15:52, schrieb Stefan Hajnoczi:
> On Sat, Jun 18, 2011 at 10:35:57AM +0200, Stefan Weil wrote:
>> Am 18.06.2011 07:13, schrieb Roy Tam:
>>> This patch fix conflicting types for 'INT32' in basetsd.h in including
>>> qemu-common.h first.
>>>
>>>
>>> Sign-off-by: Roy Tam<roytam@gmail.com>
>>> --
>>> diff --git a/ui/vnc-enc-tight.c b/ui/vnc-enc-tight.c
>>> index 87fdf35..1591df0 100644
>>> --- a/ui/vnc-enc-tight.c
>>> +++ b/ui/vnc-enc-tight.c
>>> @@ -28,6 +28,8 @@
>>>
>>> #include "config-host.h"
>>>
>>> +#include "qemu-common.h"
>>> +
>>> #ifdef CONFIG_VNC_PNG
>>> #include<png.h>
>>> #endif
>>> @@ -36,8 +38,6 @@
>>> #include<jpeglib.h>
>>> #endif
>>>
>>> -#include "qemu-common.h"
>>> -
>>> #include "bswap.h"
>>> #include "qint.h"
>>> #include "vnc.h"
>>
>> Acked-by: Stefan Weil <weil@mail.berlios.de>
>>
>> The conflicting declaration is in jmorecfg.h which is included from
>> jpeglib.h.
>
> Is the problem that the Windows headers included from qemu-common.h try
> to #define INT32?
> http://msdn.microsoft.com/en-us/library/aa383751(v=vs.85).aspx
>
> In that case I think an explicit fix is better:
>
> #ifdef _WIN32
> /* Include this before jpeglib.h for the INT32 definition */
> #include <basetsd.h>
> #endif
>
> ...followed by png/jpeg includes...
>
> Simply moving qemu-common.h provides no hints and is rather indirect.
> Someone may move it back in the future.
>
> Stefan

INT32 is declared in basetsd.h which is included from windows.h
(with some indirections) which is included from qemu-os-win32.h
which is included from qemu-common.h.

INT32 is not a #define, but a data type (typedef) and very common
for w32 compilations. Windows programmers don't include basetsd.h
directly, but usually use windows.h.

Including qemu-common.h right at the beginning (after config.h where
needed) should be good practice for QEMU source code - like this:

#include "config.h"        /* optional */
#include "qemu-common.h"
#include <system includes> /* without those that are included from 
qemu-common.h */
...
#include "other local includes"
...

As long as the maintainers don't accept patches which simply move
qemu-common.h, there is no danger. :-)

Of course a comment might be added. In most cases, I'm a great friend
of good comments, but in this special case, I don't think it is necessary.
It's a very special case of a typedef conflict caused by the mingw32
version of jpeglib (which is obviously rarely used), and it might be fixed
in a newer version of jpeglib (so the comment would be no longer
valid, and nobody would notice that).

Stefan

  reply	other threads:[~2011-06-23 15:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18  5:13 [Qemu-devel] [PATCH] fix MinGW compilation when --enable-vnc-jpeg is specified Roy Tam
2011-06-18  8:35 ` [Qemu-trivial] " Stefan Weil
2011-06-18  8:35   ` Stefan Weil
2011-06-23 13:52   ` [Qemu-trivial] " Stefan Hajnoczi
2011-06-23 13:52     ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-06-23 15:05     ` Stefan Weil [this message]
2011-06-23 15:05       ` Stefan Weil
2011-06-24  5:30       ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2011-06-24  5:30         ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-06-26 18:06       ` [Qemu-trivial] [Qemu-devel] " Blue Swirl
2011-06-26 18:06         ` [Qemu-devel] [Qemu-trivial] " Blue Swirl
2011-06-26 20:03         ` [Qemu-trivial] [Qemu-devel] " Stefan Weil
2011-06-26 20:03           ` [Qemu-devel] [Qemu-trivial] " Stefan Weil
2011-06-26 20:26           ` [Qemu-trivial] [Qemu-devel] " Blue Swirl
2011-06-26 20:26             ` [Qemu-devel] [Qemu-trivial] " Blue Swirl
2011-06-27  2:37             ` [Qemu-trivial] [Qemu-devel] " TeLeMan
2011-06-27  2:37               ` [Qemu-devel] [Qemu-trivial] " TeLeMan
2011-06-27  4:15               ` [Qemu-trivial] [Qemu-devel] " Roy Tam
2011-06-27  4:15                 ` [Qemu-devel] [Qemu-trivial] " Roy Tam
2011-06-27  5:40               ` Stefan Weil
2011-06-27  5:56                 ` Roy Tam
2011-06-27 17:22                   ` Stefan Weil
2011-06-30 15:26                     ` Paolo Bonzini

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=4E03564A.5060201@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=roytam@gmail.com \
    --cc=stefanha@gmail.com \
    /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.
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.