From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] quick gtk2.c update
Date: Tue, 21 Jun 2005 00:28:44 -0400 [thread overview]
Message-ID: <20050621042844.GA13691@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <000c01c5760d$10edf5d0$334d21d1@organiza3bfb0e>
On Mon, Jun 20, 2005 at 09:58:06PM -0500, jeebs@yango.us wrote:
> Okay, I didn't know that. (Or I forgot about it.) That means I was running
> SDL.
>
> (That also means that even if it's ends up running in SDL mode, it still
> wants all those GTK libraries available. If it isn't using GTK, then it
> shouldn't need them.)
>
Perhaps you are right (it is less of an issue in Linux since most workstations
have GTK libraries installed anways ... if you have SDL then you probably have
GTK as well). However, this approach would a) require introducing dlopen()/
LoadLibrary() into qemu in the right places (something I really hesitate to do)
or b) require a link against glib for all cases (not just the GTK case) and
use glib code to handle that (something I am even more relutant to do).
> Using that option now, I'm getting an error when I try to run qemu.
>
> ***
> Incompatable build! The code using GTK+ thinks GtkBox is of different size
> than it actually is in this build of GTK+.
>
> On Windows, this probably means that you have compiled your code with gcc
> without the -fnative-struct (or -mms-bitfileds) switch, or that you are
> using an unsupported compiler.
> ***
>
> No idea what it really means. Other than what it actually says.
>
This is a particularly perplexing error, considering that a) this error should
only show up if you 1) use a MSVC compiled GTK with a mingw/cygwin compiled
app or 2) use a mingw/cygwin compiled GTK with a MSVC compiled app. Since you
used mingw for both, I have not the slighest clue why this occurs. Especially
since I do not use GtkBox anywhere in the gtk code. (I don't use any sort of
Gtk Container period... other than GtkWindow.) There is also c) mixing GTK 2.2
and GTK 2.4 (or possibly GTK 2.4 and GTK 2.6) headers and libraries together
(e.g. including the GTK 2.2 headers in qemu but using the GTK 2.4 libraries
or something).
Technically, it means that the sizes of the structure types don't match, which
means that the library binary (GTK) and the application binary (qemu) are not
compatible.
It is possible that the 2 different mingw environments could have introduced
incompatibilities (a very remote possibility). Perhaps recompiling GTK and
its dependencies inside the new mingw environment would produce valid libraries.
Or it might trash the new environment completely...*shrug*
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-06-21 4:34 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 19:09 [Qemu-devel] quick gtk2.c update Jim C. Brown
2005-06-19 22:25 ` Sebastien Bechet
2005-06-20 0:01 ` Jim C. Brown
2005-06-19 22:57 ` jeebs
2005-06-19 23:53 ` Jim C. Brown
[not found] ` <002c01c57535$60064fb0$334d21d1@organiza3bfb0e>
2005-06-20 1:59 ` Jim C. Brown
2005-06-21 2:27 ` jeebs
2005-06-21 2:39 ` Jim C. Brown
2005-06-21 2:58 ` jeebs
2005-06-21 4:28 ` Jim C. Brown [this message]
2005-06-21 10:45 ` Jernej Simončič
2005-06-21 16:27 ` jeebs
2005-06-21 17:20 ` Jernej Simončič
2005-06-21 19:40 ` jeebs
2005-06-21 20:22 ` Jernej Simončič
2005-06-21 21:19 ` jeebs
2005-06-21 22:24 ` Jim C. Brown
2005-06-21 22:45 ` jeebs
2005-06-21 23:58 ` Jim C. Brown
2005-06-22 4:14 ` jeebs
2005-06-22 5:15 ` Damien Mascord
2005-06-22 9:31 ` Jernej Simončič
2005-06-22 12:31 ` Jim C. Brown
2005-06-22 9:16 ` Jernej Simončič
2005-06-22 13:17 ` Jim C. Brown
2005-06-22 18:36 ` Jim C. Brown
2005-06-22 18:53 ` Jim C. Brown
2005-06-22 20:59 ` Jim C. Brown
2005-06-23 2:26 ` jeebs
2005-06-24 0:32 ` Jim C. Brown
2005-06-26 16:13 ` Jim C. Brown
2005-06-27 17:11 ` jeebs
2005-06-27 18:15 ` Jim C. Brown
2005-06-22 13:22 ` Jim C. Brown
2005-06-22 3:53 ` Herbert Poetzl
2005-06-22 12:41 ` Jim C. Brown
2005-06-21 21:52 ` Jim C. Brown
2005-06-21 19:45 ` Jim C. Brown
2005-06-21 20:32 ` [Qemu-devel] Build environment image Tim Walker
2005-06-24 17:19 ` Tim Walker
2005-06-24 17:48 ` John R. Hogerhuis
2005-06-24 18:24 ` Christian MICHON
2005-06-24 18:41 ` John R. Hogerhuis
2005-06-24 18:41 ` Christian MICHON
2005-06-24 19:09 ` jeebs
2005-06-24 19:13 ` jeebs
2005-06-24 20:25 ` John R. Hogerhuis
2005-06-24 20:52 ` jeebs
2005-06-28 18:39 ` Jim C. Brown
2005-06-24 21:30 ` Tim Walker
2005-06-24 21:55 ` John R. Hogerhuis
2005-06-24 22:46 ` [Qemu-devel] " Ronald
2005-06-24 18:07 ` [Qemu-devel] " Christian MICHON
2005-06-21 10:42 ` [Qemu-devel] quick gtk2.c update Jernej Simončič
2005-06-21 12:36 ` Jim C. Brown
2005-06-21 16:30 ` jeebs
2005-06-21 17:25 ` Jernej Simončič
2005-06-21 10:39 ` Jernej Simončič
2005-06-21 10:32 ` Jernej Simončič
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 21:19 Christian Bourque
2005-06-27 21:37 ` Brad Campbell
2005-06-28 1:04 ` Jim C. Brown
[not found] ` <a6ee49d305062720121d6fcc4e@mail.gmail.com>
[not found] ` <a6ee49d30506272028f772930@mail.gmail.com>
[not found] ` <20050628033526.GA23166@jbrown.mylinuxbox.org>
[not found] ` <a6ee49d3050628075662b7ec4c@mail.gmail.com>
2005-06-28 18:46 ` Jim C. Brown
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=20050621042844.GA13691@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).