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: "cygwin" Cc: "Charles Wilson" Subject: Re: [avail for test] libtool-devel-20030121-1 Date: Sun, 16 Feb 2003 15:11:17 +0100 Message-ID: <001401c2d5c5$45fdcdd0$755f07d5@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 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal >convenience libs do not count. You can still link a DLL with convenience libs, because it is assumed that a true convenience lib is built by your project, for your project, and only for your project -- it is not available to "outside users" and therefore there can never be any mismatch between the symbols provided by (part of) the DLL and those provided by the "real" static library. >The prohibition is on OUTSIDE static dependencies. For instance, suppose you only have libz.a. Now, you >build cygkde.dll (or libkde.so on some unixoid platform) which depends on libz.a. Now, if I build chuckclient.exe which depends on the kde shared lib, and on -lz, I could possibly get a symbol conflict. >[This is actually more of an issue if I were trying to build chucklib.dll] > So, the libtool folks prohibited this behavior (for this reason, and also because it plays havoc with libtool's attempt to keep track of, via libfoo.la, the dependencies of each created sharedlib). > But don't worry about convenience libs; those are fine. Thanks for this hints. After some analyse afterwards I recognized, that the original kde libtool stuff contains a bug in building convenience libraries. It does not include any object files in special cases of using libtool flags, which let me go on a wrong way. Regards 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/