From: Filip Navara <filip.navara@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT 537fe2d] Make sure to use SDL_CFLAGS everywhere we includeSDL headers
Date: Mon, 22 Jun 2009 07:02:21 +0200 [thread overview]
Message-ID: <5b31733c0906212202h2e77804aq7e856f1dd2f016e4@mail.gmail.com> (raw)
In-Reply-To: <4A3EC618.2000200@codemonkey.ws>
On Mon, Jun 22, 2009 at 1:45 AM, Anthony Liguori<anthony@codemonkey.ws> wrote:
> Filip Navara wrote:
>>
>> Please note that this commits breaks the Win32 port in several ways. First
>> problem is the SDL_main definition as already pointed out on the mailing
>> list. The other problem is that default mingw32 builds of SDL redirect
>> stderr/stdout through the SDL_main hack (and in incorrect way too, but I
>> will leave that for the SDL folks), so it's nearly impossible to getconsole
>> output - ie. error messages or help.
>
> I have a fix in queue, but...
>
> For mingw32 we don't want to use SDL_main?
I guess a cleaner approach would be to use SDL_main to keep the code
simple and portable. I've seen some crashes in the the past that could
be related to the DirectX initialization in the SDL's main wrapper. On
the other hand it requires a custom SDL build (only libSDLmain.a, not
the sdl.dll) and that should be documented at least.
> But we want to use it for OS X?
For OS X it's absolutely necessary, it initializes the QuickDraw libraries.
Best regards,
Filip Navara
next prev parent reply other threads:[~2009-06-22 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906162031.n5GKVkTW025657@d01av03.pok.ibm.com>
2009-06-21 10:02 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 537fe2d] Make sure to use SDL_CFLAGS everywhere we includeSDL headers Filip Navara
2009-06-21 10:15 ` Filip Navara
2009-06-21 23:45 ` Anthony Liguori
2009-06-22 5:02 ` Filip Navara [this message]
2009-06-22 5:17 ` Filip Navara
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=5b31733c0906212202h2e77804aq7e856f1dd2f016e4@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).