re: building win32/wine .exe's

[Dan Kegel]

Nik wrote:
> [I build my Windows apps on Win2k.  How can I do it on Linux?
>  winegcc doesn't seem the right way.]

Depends.  If your apps use C++, and you need to be able to
access non-COM C++ DLLs compiled by other folks, I bet
the best way to go is just run the same development tools
you used on Win2k under Wine.
You might be able to just run the Visual C++ setup under Wine
and get the IDE running.  Or if the commandline is enough for you,
see http://kegel.com/wine/cl-howto.html for how I used to set that up.

Or, if you can get away with using Mingw instead of Microsoft's compiler,
see http://www.winehq.com/site/docs/winedev-guide/cross-compiling-tests
for info about how to set up a mingw cross-compiler.
- Dan

building win32/wine .exe's

[NikNot]

On 5/30/06, Dan Kegel  wrote:
> Nik wrote:
> > [I build my Windows apps on Win2k.  How can I do it on Linux?
> >  winegcc doesn't seem the right way.]

...
> Or, if you can get away with using Mingw instead of Microsoft's compiler,
> see http://www.winehq.com/site/docs/winedev-guide/cross-compiling-tests
> for info about how to set up a mingw cross-compiler.

Thank you Dan for your kind help. Indeed, as my "clover" example
implies, our C programs are probably as straightforward as Win32
software gets, and we actually use both MS C and MinGW when we build
them under Win2K/XP. One more question, if I may: where would I find
an example of a makefile or shell script that uses  MingW32 on Linux,
once installed as your reference above suggests?

Nik N.