Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To:	<cygwin AT cygwin DOT com>, <binutils AT sources DOT redhat DOT com>
Subject:	RE: [Patch] skipping import libraries for performance reasons - direct auto-import of dll's
Date:	Wed, 27 Nov 2002 00:38:03 +0100
Message-ID:	<001b01c295a4$dcc0e740$0aa807d5@BRAMSCHE>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<20021126195553.GB6605@redhat.com>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

> >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 ?
>
> It doesn't matter what cygwin uses.  Cygwin is an example.  Changing
> cygwin doesn't solve the issue for some other DLL.  Telling anyone that
> they have to reorganize their projects to accommodate 'ld' is pretty
> obviously the wrong thing to do.

Chris, please remeber, that this is an additional feature, not a hard rule. You
can, but you aren't bound to it.

Second ld on platforms with only shared libraries and static libs does give you
another choice, so on them the programmers have to live with this and I assume
that there are more platforms where ld uses this case as otherwise.

Anyway, that isn't what I have tried so say. The main meaning is "You can skip
import libraries for mostly cases by a symbolic link to the respective dll" and
second "Where are the reasons that this splitting should not be possible for the
cygwin dll"

Ralf


--
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/

- Raw text -