Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 18:14:27 +0100 (BST) Message-Id: <200005261714.SAA52440@ceratops> From: Jon Cook To: dj AT delorie DOT com CC: cygwin AT sourceware DOT cygnus DOT com In-reply-to: <200005261632.MAA24358@envy.delorie.com> (message from DJ Delorie on Fri, 26 May 2000 12:32:45 -0400) Subject: Re: ld -shared >> "DJ" == DJ Delorie writes: Thanks for your response. DJ> You have to link against an import library that defines where b DJ> comes from. DLLs work differently than shared libraries. 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!). I've played around with creating DLLs using import libraries, but I'm not sure if they will work for my situation. I have 3 libraries: a base library, A, and two extra ones, B and C, which add extra functionality to A. B and C are independent to each other, but both reference A. For some applications I link solely with A, but other applications are linked against one or both of B and C plus the base library A (this is linking under Unix). Hope this make sense! Making a DLL for A is straight forwards. DLLs for B and C are also easy to create in isolation, they both use A's import library. 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. Thanks for you help. Cheers, Jon -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com