qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Win32 build
Date: Mon, 10 Jan 2005 17:29:58 +0100	[thread overview]
Message-ID: <pan.2005.01.10.16.29.57.597990@reply.to> (raw)
In-Reply-To: 41E09627.1020802@volny.cz

Le Sun, 09 Jan 2005 03:25:43 +0100, Filip Navara a écrit :

> Changes:
> - Add x86_64-softmmu target to the build. - Fix compiling with newer
> w32api headers.
> Index: configure
> =================================================================== RCS
> file: /cvsroot/qemu/qemu/configure,v retrieving revision 1.50
> diff -u -r1.50 configure
> --- configure	3 Jan 2005 23:38:40 -0000	1.50 +++ configure	9 Jan 2005
> 01:59:41 -0000 @@ -181,7 +181,7 @@
>  strip="${cross_prefix}${strip}"
>  
>  if test "$mingw32" = "yes" ; then
> -    target_list="i386-softmmu ppc-softmmu sparc-softmmu" +   
> target_list="i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu"
>      EXESUF=".exe"
>      gdbstub="no"
>      oss="no"

Just a comment about qemu-system-x86_64, I have successfully loaded
http://bochs.sourceforge.net/guestos/linux.x86-64.bzImage on windows
98/750MHz duron. I went as far as the kernel mount the root ro and free
unused memory (on linux too) because of tls.

Another thing which can be of interest: I have updated SDL to 1.2.8,
wine (20041201) can now launch qemu.exe without setting bpp to a fixed
value in sdl.c

--- qemu-doc.texi       2004-12-20 01:18:55.000000000 +0100
+++ qemu-doc.texi.new   2005-01-10 17:25:16.582909377 +0100
@@ -1287,9 +1287,6 @@

 @end itemize

-Note: Currently, Wine does not seem able to launch
-QEMU for Win32.
-
 @section Mac OS X

 The Mac OS X patches are not fully merged in QEMU, so you should look

  reply	other threads:[~2005-01-10 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09  2:25 [Qemu-devel] [PATCH] Win32 build Filip Navara
2005-01-10 16:29 ` Ronald [this message]
2005-01-10 22:58 ` Fabrice Bellard
2005-01-10 23:56   ` 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=pan.2005.01.10.16.29.57.597990@reply.to \
    --to=look@reply.to \
    --cc=daimon55@free.fr \
    --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).