Re: [Qemu-devel] Re: QEMU News: Win32 Port

[John R. Hogerhuis]

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

I copied qemu.exe and SDL.dll from the SDL build to my vmware Win2K, and
upon running it fails as described above.

I wonder if I am missing copying over some library to the windows box.

-- John.



On Wed, 2004-03-31 at 18:25, Lennert Buytenhek wrote:
> 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
> 
> F:\>
> 
> 
> cheers,
> Lennert
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
> 
>

signature.asc
Description: This is a digitally signed message part