On Tue, Jun 28, 2005 at 10:56:55AM -0400, Christian Bourque wrote:
> Excellent!
>
> What are your plans regarding QEMU in long term? Do you still want to
> integrate a built-in GUI?
>
> I'm asking because I'm the author of JQEMU and I was wondering if I
> should continue improving the product...
On Mon, Jun 27, 2005 at 05:19:17PM -0400, Christian Bourque wrote:
> Hi Jim!
>
> Could you send a new Makefile.diff (the old one is not working with
> the latest cvs version of QEMU), I would like to test this code too...
>
> Thanks
>
> Christian
>
I just tested it myself. This patch was appli
Christian Bourque wrote:
Hi Jim!
Could you send a new Makefile.diff (the old one is not working with
the latest cvs version of QEMU), I would like to test this code too...
I had huge rejects in Makefile.target, configure and vl.h. I merged them by hand and used the latest
gtk2.c and xid_fs.c
Hi Jim!
Could you send a new Makefile.diff (the old one is not working with
the latest cvs version of QEMU), I would like to test this code too...
Thanks
Christian
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/list
On Mon, Jun 27, 2005 at 12:11:10PM -0500, [EMAIL PROTECTED] wrote:
> >
> > This should be fixed now. (At least, this now works in Windows 98 and XP.)
> > I
> > managed to combine the 3 separate mouse handlers into a single function as
> > well,
> > so there is less redundant code.
>
> It does ap
"Jm C. Brown"
>
> This should be fixed now. (At least, this now works in Windows 98 and XP.)
> I
> managed to combine the 3 separate mouse handlers into a single function as
> well,
> so there is less redundant code.
It does appear to be fixed.
> Also, I managed to get rid of the all of the GTK
On Wed, Jun 22, 2005 at 09:26:11PM -0500, [EMAIL PROTECTED] wrote:
> Now, while running my Win 3 test image, I notice that double clicking
> doesn't work. I couldn't get anything to open up no matter how fast I
> clicked.
>
This should be fixed now. (At least, this now works in Windows 98 and
On Wed, Jun 22, 2005 at 09:26:11PM -0500, [EMAIL PROTECTED] wrote:
> "Jim C. Brown"
> >
> > Ok this is probably the final revision. I had the code vindicated by an
> > actual
> > Windows programmer. He says it should work fine. It should compile, run,
> > and make
>
> Okay... I compiled it and t
"Jim C. Brown"
>
> Ok this is probably the final revision. I had the code vindicated by an
> actual
> Windows programmer. He says it should work fine. It should compile, run,
> and make
Okay... I compiled it and the keys do appear to work.
That problem does appear to be fixed.
It doesn't look
On Wed, Jun 22, 2005 at 02:53:03PM -0400, Jim C. Brown wrote:
> This version of gtk2.c includes the right header file (at least according to
> MSDN).
>
> However, after some deeper examination of the issue, it looks like it would be
> better to convert the virtual key codes to the us keyboard sca
I seem to be having problems sending attachments. Hopefully this email
will get through this time.
On Wed, Jun 22, 2005 at 09:17:23AM -0400, Jim C. Brown wrote:
> Still, I work with what I have to go on. Try this gtk2.c and report any errors
> (be they compile errors or runtime errors or keyboard
On Wed, Jun 22, 2005 at 09:17:23AM -0400, Jim C. Brown wrote:
> Still, I work with what I have to go on. Try this gtk2.c and report any errors
> (be they compile errors or runtime errors or keyboard problems). Your help is
> always greatly appreciated.
>
This version of gtk2.c includes the right
On Tue, Jun 21, 2005 at 07:58:14PM -0400, Jim C. Brown wrote:
> Well, no, that isn't it. The keymap files are based on X11 keycodes, so even
> if
> you could use this option it wouldn't work at all.
>
More digging around in sdl.c revealed that SDL on Linux returns X11 keycodes
as GTK on Linux do
On Tue, Jun 21, 2005 at 07:58:14PM -0400, Jim C. Brown wrote:
> Well, no, that isn't it. The keymap files are based on X11 keycodes, so even
> if
> you could use this option it wouldn't work at all.
>
More digging around in sdl.c revealed that SDL on Linux returns X11 keycodes
as GTK on Linux do
On Wed, Jun 22, 2005 at 05:53:14AM +0200, Herbert Poetzl wrote:
> > It's a very bad idea to have the installer need to go back on to the net to
> > download something else.
> >
> > The user should get the whole thing at once.
>
I already agreed to this.
> yes, that's what hyperlinks are for, j
On Tue, Jun 21, 2005 at 11:14:50PM -0500, [EMAIL PROTECTED] wrote:
> > They should only get this library if they don't already have a copy
> > installed.
>
> Which will be practically every qemu user.
>
[ Technically not true. Most qemu users are Linux users, and most Linux users
have GTK. :) S
On Wednesday, June 22, 2005, 6:14:50, [EMAIL PROTECTED] wrote:
> Like those files actually might possibly ever get used by some other app.
> Not too likely for a Windows user.
There's quite a selection of GTK+ programs for Windows available - Gimp,
Xchat, Gaim, Ethereal, ... BTW, it doesn't neces
On Wednesday, June 22, 2005, 1:58:14, Jim C. Brown wrote:
>> > GTK libraries are not part of qemu, they are a separate resource that qemu
>> > depends on.
>> As far as the user is concerned, they are part of qemu.
> I must disagree here. If a user already has xchat 2 installed, and that person
> w
[EMAIL PROTECTED] wrote:
> Putting more stuff into the common files folders is just going to be
> 'clutter'.
>
> Things will never get used by any other application. Eventually the user
> will even entirely forget they are there.
>
> It just ends up being clutter.
Heya Jeebs,
There are nu
"Jim C. Brown"
> I must disagree here. If a user already has xchat 2 installed, and that
> person
> wants to try to use qemu with the GTK interface, they already have the
> libraries
> that they need.
>
> Including a set of GTK libraries just for qemu would not only be redundant
> in
> this cas
On Tue, Jun 21, 2005 at 05:45:12PM -0500, [EMAIL PROTECTED] wrote:
> "Jim C. Brown"
> > I disagree. I think distributing the GTK library with qemu (even for
> > windows
> > versions) is a very bad idea. At most, the qemu installer should just
> > download
> > and run the GTK installer. At most.
>
On Tue, Jun 21, 2005 at 05:45:12PM -0500, [EMAIL PROTECTED] wrote:
> > GTK libraries are not part of qemu, they are a separate resource that qemu
> > depends on.
>
> As far as the user is concerned, they are part of qemu.
>
I must disagree here. If a user already has xchat 2 installed, and that
"Jim C. Brown"
> I disagree. I think distributing the GTK library with qemu (even for
> windows
> versions) is a very bad idea. At most, the qemu installer should just
> download
> and run the GTK installer. At most.
It's a very bad idea to have the installer need to go back on to the net to
do
On Tue, Jun 21, 2005 at 04:19:33PM -0500, [EMAIL PROTECTED] wrote:
> >I'd say it's worth it, if Qemu gains a usable GUI this way. GTK+ libraries
> >are ~3,5MB download, and only need to be installed once.
>
> Putting libraries like this in a common location is always a bad thing.
> That means the
On Tue, Jun 21, 2005 at 02:40:26PM -0500, [EMAIL PROTECTED] wrote:
> >export CFLAGS="$CFLAGS -mms-bitfields"
>
> Okay, I tried that.
>
> I then did a 'make clean'. Then the config, then the regular make
>
> But running the resulting qemu is still giving the same error.
>
>
Not the slightest
"Jernej Simonèiè"
>Hmm, it's been a while since I last tried compiling Qemu, but maybe you'll
>need to edit the makefiles to actually include that flag.
That's what I did. He sent me the patch to do that.
It runs, but there are keyboard problems.
>> The gtk libraries are more than 6 meg and w
On Tuesday, June 21, 2005, 21:40:26, [EMAIL PROTECTED] wrote:
>>export CFLAGS="$CFLAGS -mms-bitfields"
> Okay, I tried that.
> I then did a 'make clean'. Then the config, then the regular make
> But running the resulting qemu is still giving the same error.
Hmm, it's been a while since I last
"Jernej Simonèiè" <[EMAIL PROTECTED]>
>> The unzip into the proper mingw directory structure.
>Did you unzip to /mingw or to /? If the latter, you'll probably have
Into the mingw directory.
That part seems to compile etc. It's the resulting program that is screwed
up some how.
>export CFLAG
On Tue, Jun 21, 2005 at 11:27:10AM -0500, [EMAIL PROTECTED] wrote:
> I downloaded the libraries and devel files from the link Jernej Simoncic
> recommended. It does seem to be a main win gtk distrib location. (As
> somebody pointed out, actually building gtk etc. under Mingw is a pita. I
> ha
On Tuesday, June 21, 2005, 18:30:07, [EMAIL PROTECTED] wrote:
>>Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and
>>compiling
>>any GTK+ program on Windows - the libraries are always built to be
>>compatible with MSVC so that you can use 1 set of libraries for all
>>programs.
> I
On Tuesday, June 21, 2005, 18:27:10, [EMAIL PROTECTED] wrote:
> I downloaded the libraries and devel files from the link Jernej Simoncic
> recommended. It does seem to be a main win gtk distrib location. (As
> somebody pointed out, actually building gtk etc. under Mingw is a pita. I
> haven't
> 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
I downloaded the libraries and devel files from the link Jernej Simoncic
recommended. It does seem to be a main win gtk distrib loc
From: "Jernej Simonèiè"
>> No idea what it really means. Other than what it actually says.
>Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and
>compiling
>any GTK+ program on Windows - the libraries are always built to be
>compatible with MSVC so that you can use 1 set of librar
On Tue, Jun 21, 2005 at 12:42:56PM +0200, Jernej Simon?i? wrote:
> On Tuesday, June 21, 2005, 4:58:06, [EMAIL PROTECTED] wrote:
>
> > No idea what it really means. Other than what it actually says.
>
> Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and compiling
> any GTK+ progra
On Tuesday, June 21, 2005, 4:58:06, [EMAIL PROTECTED] wrote:
> No idea what it really means. Other than what it actually says.
Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and compiling
any GTK+ program on Windows - the libraries are always built to be
compatible with MSVC so t
On Tuesday, June 21, 2005, 6:28:44, Jim C. Brown wrote:
> 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
> u
On Tuesday, June 21, 2005, 4:27:04, [EMAIL PROTECTED] wrote:
> I'd rather keep them in the qemu directory. Just like I do with sdl.dll
Semi-official place to put GTK+ libraries on Windows is C:\Program
Files\Common Files\GTK\2.0, and then adding bin\ subdirectory to PATH. This
is what GTK+ insta
On Monday, June 20, 2005, 3:59:11, Jim C. Brown wrote:
> 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.
Thanks to people like that I had to put detection of such broken installs to
the GTK+ installer distrib
On Mon, Jun 20, 2005 at 09:58:06PM -0500, [EMAIL PROTECTED] 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,
On Mon, Jun 20, 2005 at 09:27:04PM -0500, [EMAIL PROTECTED] wrote:
> Good news...
>
> Tonight I decided to test my Mingw/MSys environment. I built the regular
> SDL version that I've done several times before.
>
> It too failed.
>
> There's not much telling what is causing it to fail. Qemu se
"Jim C. Brown"
>> There's not much telling what is causing it to fail. Qemu seems rather
>> sensitive to the slightest change in build environment.
>
> Not the most reliable development environment.
No, it's not...
I think some of it is inherent in the GCC stuff. Others, just the general
buil
"Jim C. Brown"
Sorry I hadn't got back to you sooner, but I was busy Some good news...
Keep reading.
>> 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.
MingW's MSYS is a seperate, isola
On Sun, Jun 19, 2005 at 08:13:55PM -0500, [EMAIL PROTECTED] wrote:
> > If that one doesn't work, try this one. (The only different is that I
> > include
> > instead of )
>
> > I also attach a gdkprivate-win32.h in case yours is missing (google seems
> > to
>
> I'm not getting any errors about
On Mon, Jun 20, 2005 at 12:25:54AM +0200, Sebastien Bechet wrote:
> Hello Jim,
>
> I have no time to test your patch :-( I think I can do it in august...
I have to know how you got GdkPixbuf to work with your GTK patch.
I looked at using GdkPixbuf but it seems not flexible enough to support
the g
On Sun, Jun 19, 2005 at 05:57:46PM -0500, [EMAIL PROTECTED] wrote:
> From: "Jim C. Brown"
>
> > Minor changes to gtk2_send_mouse_move() for GTK 2.6
>
> Under Windows with MingW & MSYS, I'm still getting the same compiler error
> that I reported to you before.
>
> Along with an assortment of war
From: "Jim C. Brown"
> Minor changes to gtk2_send_mouse_move() for GTK 2.6
Under Windows with MingW & MSYS, I'm still getting the same compiler error
that I reported to you before.
Along with an assortment of warnings in the GDK stuff. Plus the usual qemu
warnings.
I'm still using the same s
Hello Jim,
I have no time to test your patch :-( I think I can do it in august...
Nevertheless, now gtk driver works (i suppose :-p), i have some old
glade files on my hard disk to add Qemu-GTK GUI.
Do you want I send it on the ML ? Maybe it can give you some idea if you
have time to continue ? I
47 matches
Mail list logo
