Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: Subject: RE: [PATCH] libtool patch for direct-linking-to-dll Date: Mon, 10 Mar 2003 20:49:03 +0100 Message-ID: <008101c2e73e$1a8297f0$dc6207d5@BRAMSCHE> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20030310173442.GI23549@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal > On Mon, Mar 10, 2003 at 08:13:16AM -0500, Charles Wilson wrote: > >I didn't realize it was a patch to rip out all of the import-lib > >building stuff, and replace it with the new link-to-dll support. > > I've been blissfully trying to avoid libtool discussions but I have to > ask my standard question of "what about hybrid libraries which contain > import symbols and actual linkable objects, like the cygwin DLL". > > I assume that this has been discussed but it's hard for me to believe > that any discussion would end with "We won't worry about them, then". > That seems to be counter to what libtool is all about. > 1. As far as I know there is no way to build hybrid libraries with libtool; only shared or static libs are allowed, so generating hybrid libraries will not be possible with libtool. 2. Linking to non-libtool generated hybrid libraries will be no problem, because for libtool they will be recognized as standard import libraries. Linking to non libtool created dlls with a symbolic link as import lib replacement (the new scheme) will be recognized as dll, which will be no problem too. 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/