Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com From: "Ralf Habacker" To: "Cygwin-Apps" Subject: RE: libtool devel package still dll crippled. Date: Sun, 14 Apr 2002 20:53:25 +0200 Message-ID: <000101c1e3e5$a8b71030$0a1c440a@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: <3CB9C1F4.5090909@ece.gatech.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal > I'm using a special patched ld (based on the > recent official > > ld) which rejects exporting of all imported > libs with a one > > line patch > > > > binutils/ld/pe-dll.c:234 > > /* Do not specify library suffix explicitly, to > allow for > > dllized versions. * > > static autofilter_entry_type autofilter_liblist[] = > > { > > { "libgcc.", 7 }, > > { "libstdc++.", 10 }, > > { "libmingw32.", 11 }, > > +// RH: workaround to allow using static libs > in multiple > > dlls > > + { ".a", 2 }, > > { NULL, 0 } > > }; > > > I really think this is a mistake. What if I want > to build a shared > library using libtool, and it is composed of a > number of object files > but also some convenience libs? And those > convenience libs contains > symbols that I want to export? I have not said, that this workaround is a general patch usable in all situations. Because KDE does create only dll's this was okay for me. Dannys patch is of course the beest solution, but it requires some (as I recognized after reviews this patch) deeply changes of the libtool implementation, which isn't not easy. :-( Ralf