Tor - cygwin build issues...

Tim Renner writes:
 > On your win32 page, you say that you have to use the -mno-cygwin
 > and -fnative-struct flags to successfully use the GTK+ binaries
 > under cygwin...  due to dll's and struct alignment.  Can you expand
 > on that a little more?

The -mno-cygwin switch means that you are not building a Cygwin
program, because the prebuilt DLLs I provide don't use Cygwin
either. In general it isn't a good idea to mix C runtimes in an
application and the libraries it uses. And Cygwin isn't just a C
runtime, it's more like a whole operating system.

The -fnative-struct switch means that struct fields (in particular,
certain bitfields and the fields following them) are aligned
identically to what MSVC does, so that the same DLL can be used both
by code compiled with gcc and code compiled with MSVC.

 > We're running into a case where we can't use -mno-cygwin,

Then you really shouldn't be using the prebuilt GLib and GTK+ DLLs for
Win32. Cygwin is a wholly different operating system, more or less.

That said, I have heard that some people claim to have used my
prebuilt DLLs also from Cygwin programs. If it happens to work, OK,
but don't expect it to necessarily work in the future, and if you run
into strange errors, you're on your own.

 > I've got our cygwin compiled program compiled and linking w/
 > glib-2.0.6 and gtk+-2.0.6, but when running, it dies with the
 > following

 >       6 [unknown (0x1974)] ? 6444 cygheap_fixup_in_child: Couldn't reserve 
 > space for cygwin's heap (0x615D0000 <0xF60000

 > Any light you or anyone else can shed on this would be very much 
 > appreciated, the more detailed the better

I wonder why nobody is offering prebuilt Cygwin versions of GLib and
GTK+. They shouldn't be hard to build on Cygwin, and patches people
have sent in to make them more Cygwin friendly have been applied, and
will be. (Hmm, except that I know I have a couple of mails from last
month regarding Cygwin and GTK+ waiting to be processed. Have
patience...)

--tml