This is the mail archive of the
mailing list for the Cygwin project.
Re: ld ---export--all --exclude-libs,?
- From: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 22 Nov 2001 07:05:20 +1100 (EST)
- Subject: Re: ld ---export--all --exclude-libs,?
--- Corinna Vinschen <email@example.com> wrote: > On Wed, Nov 21, 2001
at 07:41:58PM +1100, Danny Smith wrote:
> > Hello, I'm after some criticism, before submitting this to binutils.
> > IMO, the auto-export feature of ld needs (at least) an option to
> > whole libs from export. The following patch does that. It also adds a
> > more default lib excludes and scans for backward compat implib symbols
> > (__imp_)
> > I think this patch doesn't do enough.
> > My preference would be to exclude *all* libs by default, with a command
> > line option to explicity *include* named libs. Why? It is too easy for
> > licensed library code to sneak into dll's using --export-all. This
> > distributability (sic) of the dll and apps dependent on the dll.
> > The user may be unaware of this infection because its automatic.
> > At least make the user think about what she/he is exporting.
> > I will gladly throw away the following to work on a patch to exclude
> > libs by default if given encouragement.
> > Any comments.
> Yes, a question. First note that I'm a binutils (l)user, not a
> developer so I apologize for being thick. Now the question:
> Isn't the functionality you're searching for already in ld given by
> the --no-whole-archive options?
> gcc -shared -o cygfoo.dll $(OBJ)
> -Wl,--no-whole-archive -lbar -lbaz
> Or am I missing the point?
That does'nt do it. For example, if my dll uses lbasename from
libiberty.a, --export-all,--no-whole-archive will still export the
The --exclude-libs option would exclude those symbols from the exports.
http://shopping.yahoo.com.au - Yahoo! Shopping
- Get organised for Christmas early this year!