From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Hotmail <computers57@hotmail.com>
Cc: qemu Devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] another patch against head
Date: Wed, 28 Nov 2007 12:49:34 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711281247010.27959@racer.site> (raw)
In-Reply-To: <BAY133-DAV29F8DEB7D6C2BAE30DA3DB9760@phx.gbl>
Hi Hotmail,
On Tue, 27 Nov 2007, Hotmail wrote:
> The following is another patch against the head that lets me build it on
> Windows, as well as makes the adlib.c file debuggable.
>
> Index: Makefile
> ===================================================================
> RCS file: /sources/qemu/qemu/Makefile,v
> retrieving revision 1.136
> diff -r1.136 Makefile
> 17a18,20
> > ifdef CONFIG_WIN32
> > LIBS= -lmingw32 -mno-cygwin
> > else
> 18a22
> > endif
So you build it in Cygwin, not "on Windows".
> Index: cocoa.m
> ===================================================================
> RCS file: /sources/qemu/qemu/cocoa.m,v
> retrieving revision 1.14
> diff -r1.14 cocoa.m
> 754c754
> < [op beginSheetForDirectory:nil file:nil types:[NSArray arrayWithObjects:@"img",@"iso",@"dmg",@"qcow",@"cow",@"cloop",@"vmdk",nil]
> ---
> > [op beginSheetForDirectory:nil file:nil types:[NSArray arrayWithObjects:@"img",@"iso",@"dmg",@"qcow",@"qcow2",@"cow",@"cloop",@"vmdk",nil]
How does this help compiling on Windows?
> Index: monitor.c
> ===================================================================
> RCS file: /sources/qemu/qemu/monitor.c,v
> retrieving revision 1.87
> diff -r1.87 monitor.c
> 31a32
> > #include "qemu-timer.h"
> Index: hw/adlib.c
> ===================================================================
> RCS file: /sources/qemu/qemu/hw/adlib.c,v
> retrieving revision 1.8
> diff -r1.8 adlib.c
> 25a26
> > #include "audio/audio.h"
> 26a28
> > #include "qemu-timer.h"
Why are these needed? It appears that all other platforms build QEmu just
fine without these #includes.
But then, the answer to that riddle could be in the context. Since you
did not use the unified diff format, I have no chance to know.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-28 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:17 [Qemu-devel] another patch against head Hotmail
2007-11-28 12:49 ` Johannes Schindelin [this message]
2007-11-28 13:39 ` Samuel Thibault
2007-11-28 14:01 ` Johannes Schindelin
2007-11-28 14:09 ` Samuel Thibault
2007-11-28 14:34 ` Johannes Schindelin
2007-11-28 16:16 ` Hotmail
2007-11-28 16:35 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 17:28 Re : " Sylvain Petreolle
2007-11-30 15:35 ` Hotmail
2007-12-02 17:49 ` Thiemo Seufer
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=Pine.LNX.4.64.0711281247010.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=computers57@hotmail.com \
--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).