wine users - Sep 2009 - wine advantages over mingw

What are the advantages of using winegcc over the mingw cross compiler? 
Also, what are the differences in the header files / libs supplied with each ? 

I have an app (http://www.autohotkey.com/forum/viewtopic.php?t=46546) cross
compiling with mingw using codeblocks, and I have it working under winelib side
by side native linux code.

I wanted to translate it so it would compile with winegcc so i have to do less
wrapping of code...

Also, does anyone have winegcc configuration instructions for a free IDE
(preferably codeblocks)?

Thanks.

On Fri, Sep 4, 2009 at 00:34, tinku99<wineforum-user at winehq.org>
wrote:
> What are the advantages of using winegcc over the mingw cross compiler?
AFAIK, you can mix in native Linux code with winegcc (Which can be
very useful native user-interface components / hardware access)

tinku99 wrote:
> What are the advantages of using winegcc over the mingw cross compiler?
You can make winelib apps/libraris. That's all. You'll need Wine to run
them however. That's really the only thing you can do with winegcc.


tinku99 wrote:
> Also, what are the differences in the header files / libs supplied with
each ?
Wine always have enough headers to compile itself and all of it's tests. But
not the fill set of SDK/PSDK headers. While mingw has lots of standard SDK
headers, that some times do miss some pieces required by Wine.


tinku99 wrote:
> I have an app cross compiling with mingw using codeblocks, and I have it
working under winelib side by side native linux code.
Wine does not cross compile anything. It's using good 'ol gcc. All of
Wine's libraries are .so.

However, you can ask Wine to crosscompile all tests and some dlls. However for
that Wine uses ... mingw.