Fabrice Bellard | 1 Apr 01:36 2004

QEMU News: Win32 Port

Hi,

I commited an experimental win32 port of QEMU. I did not test it yet, 
but it compiles. It is based on Kazu port, but I made heavy 
modifications to minimize the number of ifdefs and to factorize the 
"dyngen" utility code.

In order to compile it, look at 
http://www.h7.dion.ne.jp/~qemu-win/PortingTips-en.html.

Feel free to submit any patches, in particular for audio, network 
redirector or native GUI for win32.

Note that I won't accept any patch to make it compile with MSVC. You 
must use MSYS/MinGW in order to compile the win32 port of QEMU.

Fabrice.
Fabrice Bellard | 1 Apr 01:45 2004

Re: QEMU News: Win32 Port

Fabrice Bellard wrote:
> Hi,
> 
> I commited an experimental win32 port of QEMU. I did not test it yet, 
> but it compiles. It is based on Kazu port, but I made heavy 
> modifications to minimize the number of ifdefs and to factorize the 
> "dyngen" utility code.
> 
> In order to compile it, look at 
> http://www.h7.dion.ne.jp/~qemu-win/PortingTips-en.html.

I should not have given this URL because Cygwin is _not_ needed to 
compile QEMU. Instead use the following steps (taken from the FFmpeg 
project doc):

* Install the current versions of MSYS and MinGW from 
http://www.mingw.org/. You can find detailed installation instructions 
in the download section and the FAQ.

* Download the MinGW development library of SDL 1.2.x 
(SDL-devel-1.2.x-mingw32.tar.gz) from http://www.libsdl.org. Unpack it 
in a temporary place, and unpack the archive i386-mingw32msvc.tar.gz in 
the MinGW tool directory. Edit the sdl-config script so that it gives 
the correct SDL directory when invoked.

* Extract the current CVS version of QEMU.

* Start the MSYS shell (file 'msys.bat').

* Change to the QEMU directory and launch './configure' then 'make'. If 
(Continue reading)

John R. Hogerhuis | 1 Apr 01:51 2004
Picon

Re: QEMU News: Win32 Port

So at one point and who should post a story to Slashdot or another news
site about Kazu's port? I'd personally call this newsworthy. And it
could bring a spike of new interest to the project that could help get
the remaining drivers knocked out, and probably even more interest for
QEMU generally.

-- John.
_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/qemu-devel
Fabrice Bellard | 1 Apr 02:06 2004

Re: QEMU News: Win32 Port

John R. Hogerhuis wrote:
> So at one point and who should post a story to Slashdot or another news
> site about Kazu's port? I'd personally call this newsworthy. And it
> could bring a spike of new interest to the project that could help get
> the remaining drivers knocked out, and probably even more interest for
> QEMU generally.

Before making an "official" announce, it is better to wait for the 0.5.3 
release as it contains big improvements compared to the 0.5.2 (I will 
release it before the end of the week).

Fabrice.
Lennert Buytenhek | 1 Apr 04:25 2004

Re: Re: QEMU News: Win32 Port

On Thu, Apr 01, 2004 at 01:45:58AM +0200, Fabrice Bellard wrote:

> >I commited an experimental win32 port of QEMU. I did not test it yet, 
> >but it compiles. It is based on Kazu port, but I made heavy 
> >modifications to minimize the number of ifdefs and to factorize the 
> >"dyngen" utility code.
> >
> >In order to compile it, look at 
> >http://www.h7.dion.ne.jp/~qemu-win/PortingTips-en.html.
> 
> I should not have given this URL because Cygwin is _not_ needed to 
> compile QEMU. Instead use the following steps (taken from the FFmpeg 
> project doc):

I guess cross-compiling for Windows from a linux host isn't supported?
These are the problems I stumble over when I try to do just that:
* The SDL probe in 'configure' uses the host's CC instead of the target
  CC, causing the probe to fail.
* After hacking around that, it appears that dyngen is compiled as a .exe
  instead of a host binary, causing Wine to launch whenever dyngen is used
  in the build process.
* -lutil is used for final linking, but libutil.a is a component of glibc,
  and I didn't dare trying to build it for Windows (does that even work? :)
  It doesn't even seem to be needed -- removing the '-lutil' causes a
  qemu.exe to be built anyway.

After qemu.exe is built, it doesn't seem to work.  It does run, but simply
refuses to output anything:

F:\>qemu.exe
(Continue reading)

John R. Hogerhuis | 1 Apr 06:07 2004
Picon

Re: Re: QEMU News: Win32 Port

I am working on doing a cross compile right now...

The first hurdle was dyngen.exe. It ran fine for me with wine, though (I
am using crossover office version of wine though... don't know if that
matters).

Alternatively I posted a patch to this list which will allow you to
generate an op.h which has the binary code in it as source code in op.h
so you can generate the op.h on Linux and use it in the mingw build.
Kludgy but works.

Now I'm working on building SDL. I'll post here with instructions once I
get everything working... I can't imagine this should be too hard...

-- John.

_______________________________________________
Qemu-devel mailing list
Qemu-devel <at> nongnu.org
http://mail.nongnu.org/mailman/listinfo/qemu-devel
John R. Hogerhuis | 1 Apr 09:09 2004
Picon

Re: Re: QEMU News: Win32 Port

I get the same behavior... qemu that is built just silently exits, with
no output.

The SDL probe can be fixed by moving it down just after cc is redefined
to include the cross compiler prefix.

I did the same thing you did and removed the -lutil prefix to get the
last step to compile.

There does seem to be one more issue in the install for the main
Makefile... it wants to copy a the qemu-mkcow utility but the TOOLS
macro is already set to nothing because CONFIG_WIN32 is defined.

Some details:

I am using the following to build SDL:

./configure --host=i586-mingw32msvc --disable-nasm
--prefix=/home/john/projects/SDL-1.2.7

I added /home/john/projects/SDL-1.2.7 to beginning of my path so that
sdl-config would be found there.

Then I configured QEMU to make the cross compiler prefix under the
--enable-mingw32 option to match my compiler. I ran

./configure --enable-mingw32 --prefix=/home/john/projects/qemu
make install

qemu.exe gets created in i386-softmmu
(Continue reading)

Renzo Davoli | 1 Apr 09:32 2004
Picon

Compiling Qemu on Debian/SID

Along with (obviously) all the needed libraries with their corresponding
_dev packets I had to change the config-host.mak file by adding
-lgpm at the end of SDL_STATIC_LIBS
(I know that config-host.mak should not be changed by hand)

Reading the configure script the problem appears to be in:
sdl-config --static-libs 
that does not put -lgpm in its output.

renzo
Rudi Lippert | 1 Apr 09:43 2004
Picon

Re: QEMU News: Win32 Port - Release Schedule


come to this - is there a way to tighten the release schedule in order to have 
new versions come out more frequently?
this would allow distributors to build up-to-date packages of qemu, and we 
might even be in the news every month.
personally, i don't like building from cvs, since you can never know if it 
will even compile. the old gentoo-issue, you know. packages made by people 
with a better understanding of things than i (and many others) have, would 
compile, so we would have a lot more people testing qemu and providing 
feedback.
if you believe that a release is compileable but not quite release-worthy, you 
could for example name it 0.5.3pre1 or something like that.

i just believe that more releases mean more testers and more publicity.

my €0.02

On Thursday 01 April 2004 02:06, Fabrice Bellard wrote:
> Before making an "official" announce, it is better to wait for the 0.5.3
> release as it contains big improvements compared to the 0.5.2 (I will
> release it before the end of the week).
>
> Fabrice.
Lennert Buytenhek | 1 Apr 10:07 2004

Re: Re: QEMU News: Win32 Port

On Wed, Mar 31, 2004 at 08:07:15PM -0800, John R. Hogerhuis wrote:

> The first hurdle was dyngen.exe. It ran fine for me with wine, though (I
> am using crossover office version of wine though... don't know if that
> matters).

(It doesn't matter, runs fine with regular wine.)

> Now I'm working on building SDL. I'll post here with instructions once I
> get everything working... I can't imagine this should be too hard...

Seemed rather straightforward to me..

--L

Gmane