Part 1: tools for win32 development in linux

emerge the following packages to create a development environment:


dev-util/xmingw-binutils
dev-util/xmingw-gcc
dev-util/xmingw-runtime
dev-util/xmingw-w32api
app-emulation/wine

Use the following as a template for win32 makefiles:

CC=i386-mingw32msvc-gcc
CFLAGS=-O2 -pipe -std=c99 -mno-cygwin -mno-sse -mno-sse2 -mno-mmx -mthreads -DWIN32 -D_WIN32 -D_WINDOWS

helloworld.exe: helloworld.o
$(CC) $(CFLAGS) -luser32 -o $@ $?

helloworld.o: helloworld.c helloworld.h
$(CC) $(CFLAGS) -o $@ -c $<

NOTE: Now is not a good time to rice out your cflags. Debugging win32 code is hard enough without the compiler playing tricks on you.

To test your new win32 program:

wine ./helloworld.exe

Part 2 will talk about how to create win32 DLLs and import libraries.

*EDIT* I’m sick of all the lame losers out there that keep spamming my blog, so no more comments until something can be worked out

3 thoughts on “Part 1: tools for win32 development in linux

  1. Daniele Gaffuri

    I had to use gcc-3.4.4-r1 to compile xmingw-binutils, because 4.0.2-r2 gives an error. If someone is interested I’ll retry and post the exact message.

    Reply
  2. Ian Monroe

    The hard part would be to setup all the libraries and such I’d guess.

    Like it’d be cool for when KDE 4 comes around to be able to make the Windows builds on Linux. But then you’d need to have loads of supporting libraries and such to compile something like amaroK.

    Hopefully I’m wrong though. :)

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>