Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Fri, 26 May 2000 14:16:06 -0400
Message-Id:	<200005261816.OAA25066@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	cookj AT cs DOT man DOT ac DOT uk
CC:	cygwin AT sourceware DOT cygnus DOT com
In-reply-to:	<200005261714.SAA52440@ceratops> (message from Jon Cook on Fri,
	26 May 2000 18:14:27 +0100 (BST))
Subject:	Re: ld -shared
References:	<200005261714 DOT SAA52440 AT ceratops>

> Is there any plans to make them work in the same way as shared
> libraries on a Unix machine (I dont know if this is possible or even
> desirable!). 

Possible, yes, but not practical.  Windows already has a mechanism
(dlls) so the gains aren't worth the effort.  If you want real shared
libraries, get Interix, which runs on the posix side of NT, or get
Linux.

> I can see how linking an application against either A, B or C will
> work (B and C should automatically include A and so I would not need
> to link explicitly against this). But, can I link an application
> against both B *and* C without causing a problem since A will now be
> included twice.

Yes.  Windows resolves those issues when it loads the DLLs.  Your
program doesn't even need to know that B and C use A, since it only
sees the import libraries, not the whole DLL's objects.

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

- Raw text -