This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: [Patch] skipping import libraries for performance reasons - direct auto-import of dll's
- From: "Ralf Habacker" <Ralf dot Habacker at freenet dot de>
- To: <cygwin at cygwin dot com>, <binutils at sources dot redhat dot com>
- Date: Tue, 26 Nov 2002 08:30:01 +0100
- Subject: RE: [Patch] skipping import libraries for performance reasons - direct auto-import of dll's
> On Mon, Nov 25, 2002 at 01:46:50PM +0100, Ralf Habacker wrote:
> >3. ld works more like the linux version. There are only static archives and
> >shared libraries which could be linked directly without the
> indirection of using
> >import libraries. This simplifies for example libtool handling.
>
> I don't see how. If anything it would complicate libtool handling
> since libtool
> would have to know about both import libraries and dlls. You can't just give
> up on import libraries, if for no other reason than some libraries (like
> cygwin's for instance) contain a combination of import data and static data.
This and perhaps other libraries may be an exception, but couldn't this splitted
like linux does ?
If I remember right, they uses a standard lib like glibc, which may be a shared
lib and some kind of startupcode in an objectfile (static), which may be
different for executable or dll's or other kinds of output. Why does cygwin uses
a specific way ?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/