Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 14 May 1999 18:37:46 -0400
Message-Id: <199905142237.SAA32066@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: Fieldhouse AT logica DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <E08D1D96ABE2D2119B3300A0C94D23062B2FDF@hopper.logica.co.uk>
	(Fieldhouse AT logica DOT com)
Subject: Re: Using gcc/egcs with MSVC .lib files
References:  <E08D1D96ABE2D2119B3300A0C94D23062B2FDF AT hopper DOT logica DOT co DOT uk>


> but ld can't build with .obj/.lib.

Correct.  First, ld has problems with some .objs produced by MS tools;
this is an object-level problem so it won't matter if they're in a
library or not.  Second, MS's import libraries don't have the required
hooks in them for ld to properly link them.  Some objects may work
fine; others may not.

I've been working with a developer from Interix to fix the gnu tools
to properly deal with these issues and various other cleanup items,
but it's a *big* project.  Some preliminary changes may be available
soon, but it's not at the top of my current priority list.  Note that
one of the planned changes is to fix COMDAT sections, but it *may*
break compatibility with old C++ libraries (we plan on supporting the
broken way also if we can).

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com