From: "Jim C. Brown" <jma5@umd.edu>
To: jeebs@yango.us
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] quick gtk2.c update
Date: Sun, 19 Jun 2005 21:59:11 -0400 [thread overview]
Message-ID: <20050620015911.GA17675@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <002c01c57535$60064fb0$334d21d1@organiza3bfb0e>
On Sun, Jun 19, 2005 at 08:13:55PM -0500, jeebs@yango.us wrote:
> > If that one doesn't work, try this one. (The only different is that I
> > include
> > <gdk/win32/gdkwin32.h> instead of <gdk/gdkwin32.h>)
>
> > I also attach a gdkprivate-win32.h in case yours is missing (google seems
> > to
>
> I'm not getting any errors about that. But maybe the build isn't getting
> that far. I'll go ahead and drop it into the qemu directory just in case.
>
If you are not getting any errors about it, then you don't need it.
Dropping it into the qemu directory probably wouldn't help at all. Shouldn't
mess anything up, though.
> Okay... In gdk_set_window_pointer.c, you include
> #include <gdk/win32/gdkwin32.h>
>
> For my mingw / msys enviornment, that should be
> #include <gdk/gdkwin32.h>
>
> Fixing that, I do get a sucessful build.
>
Ok. I've seen it done both ways so I wasn't sure which was correct for
current GTK-win32.
> However, it doesn't run.
>
> Qemu, as usual, doesn't print out anything that could possibly be of any use
> to somebody having trouble.
>
> So, I dropped down to the command line and ran it again.
>
> This time I got a number of Windows errors saying it couldn't find the
> proper gtk etc. libraries.
>
> So I copied about 6 meg of library files to my qemu test directory.
>
Strange. I'm not too familiar with the Windows equivulent of LD_LIBRARY_PATH.
I did find a GTK Windows tutorial at http://wolfpack.twu.net/docs/gtkwin32/,
but that says to install the dlls to the System folder.
> This time it stopped complaining, but after a couple seconds, a Windows box
> poped up saying an error occured and that it was shutting qemu down.
>
> I don't have any further information to give you. Sorry.
>
I could make a modified gtk2.c which would printf() more debugging information.
One that would print out enough information to tell me exactly which part of the
code was causing the error and what the error was.
If you are willing to help me do the debugging, I'll email you the modified code
as well as detailed instructions and wait back for the results. This will have
a slightly higher time commitment though.
Thanks for helping me get this far.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-06-20 2:00 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 [this message]
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
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=20050620015911.GA17675@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=jeebs@yango.us \
--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).