This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE[2]: Patch to pe-dll.c: Allow exclusion of whole libs with --export-all


> -----Original Message-----
> From: binutils-owner@sources.redhat.com
> [mailto:binutils-owner@sources.redhat.com]On Behalf Of Danny Smith
> Sent: Saturday, November 24, 2001 7:55 AM
> To: binutils
> Subject: RE[2]: Patch to pe-dll.c: Allow exclusion of whole libs with
> --export-all
>
>
>  --- Danny Smith <danny_r_smith_2001@yahoo.co.nz> wrote: > Date: Sat, 24
> Nov 2001 14:30:56 +1100 (EST)
> > From: Danny Smith <danny_r_smith_2001@yahoo.co.nz>
> > Subject: RE: Patch to pe-dll.c: Allow exclusion of whole libs with
> > --export-all
> > To: binutils <binutils@sources.redhat.com>
> >
> > > "Ralf Habacker" <Ralf dot Habacker at freenet dot de>
> > wrote:
> > > -----Original Message-----
> > >> From: binutils-owner@sources.redhat.com
> > >> [mailto:binutils-owner@sources.redhat.com]On Behalf Of Danny Smith
> > >> Sent: Thursday, November 22, 2001 2:12 AM
> > >> To: binutils
> > >> Subject: Patch to pe-dll.c: Allow exclusion of whole libs with
> > >> --export-all
> > >>
> > >>
> > >> The auto-export feature of ld for pe-dll targets needs an option to
> > exclude
> > >> whole libs from export. The following patch allows exclusion of
> > specific
> > or
> > >> all libs.
> > >>
> > >> It also adds a few more default lib excludes and scans for backward
> > >> compat implib symbols (__imp_)
> > >>
> > <snip>
> >
> > > How would libtool handle this ?
> >
> > > Ralf
> >
> > I don't quite know what your asking.  How does libtool handle
> > --exclude-symbols?

I mean, that libtool has to be extended to handle this feature in the case of creating a dll
and using static libs.
Currently I uses a workaround with setting ld's "no whole archive" flag and not setting the
libtool "whole-archive-flag" that libtool let unpacking all used static archives temporary
and link the contained object files directly with.

Currently I don't know if libtool could distinguish between a static lib that should not be
exported and one that should be.
Especially for the kde-cygwin project, there are severell dll's that are build from more than
one static libs. In this case, each static lib has to be exported. In the case that one
static lib is used by more than one dll it
must not be exported.

May be that this list isn't the right place for discussion of this topic, but I like to
remark that such a functionality has some interactions with libtool. Currently I have no
solution for this.

Regards Ralf



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]