Re: [Mingw-users] Re: [gimpwin-dev] glib under mingw32 debian crosscompiler, problem with windres : gmodule-win32res.lo: file not recognized:File format not recognized
From: Christof Petig <christof petig-baender de>
To: Christopher Faylor <cgf redhat com>
Cc: James Michael DuPont <mdupont777 yahoo com>, dia-list gnome org,gimpwin-dev yahoogroups com, MinGW-users lists sourceforge net,steven obrien2 ntlworld com
Subject: Re: [Mingw-users] Re: [gimpwin-dev] glib under mingw32 debian crosscompiler, problem with windres : gmodule-win32res.lo: file not recognized:File format not recognized
Date: Mon, 02 Sep 2002 08:45:14 +0200
Christopher Faylor schrieb:
> On Fri, Aug 30, 2002 at 04:03:28PM +0200, Christof Petig wrote:
>
>>[Summary: Cygwin is good to compile programs on win32 with minimal
>>porting effort, but a stable port should use MinGW]
I meant build target not compiler tool chain.
> Summary: If you want to ignore all of the work that has gone into
> -mno-cygwin to make it work reliably, then use MinGW.
That was not what I said. I said nothing about the cygwin toolchain but
about the build target.
Last year the -mno-cygwin (I need C++ & libtool !!!) support was suited
to give me a lots of headaches and made me angry to have even tried. I
never got a reliable gtkmm.dll out of that! And I tried for weeks.
From my experience and reading on the MinGW list:
- there seemed to be no one at cygwin interested in reliably maintaining
the no-cygwin part.
- Mixing header files and import libraries was easily done within
cygwin. The result normally failed to link or crashed randomly
- C++ support for -mno-cygwin was severely damaged
And I was not aware that it improved _that_ much. I still can't believe
that the cygwin toolchain will give you a -mno-cygwin environment
without lots of (undocumented?) 'never do this' and 'do it this way'.
Sorry, too much negative personal experience with cygwin on my side
Christof