Re: Excude whole libs when building w32 dlls with -export-all [Refresh]

2002-05-30 Thread Charles Wilson
FWIW, it appears that this patch was committed on 21 May 2002. --Chuck Danny Smith wrote: The previous post had incorrect subject heading. This is a repost. Sorry. This is a refresh of: http://sources.redhat.com/ml/binutils/2002-04/msg00472.html The patch allows exclusion of

RE: Excude whole libs when building w32 dlls with -export-all [Refresh]

2002-05-20 Thread Danny Smith
The previous post had incorrect subject heading. This is a repost. Sorry. This is a refresh of: http://sources.redhat.com/ml/binutils/2002-04/msg00472.html The patch allows exclusion of symbols in specified libs (optionally all libs) from export table when producing dll's using ld --shared.

RE: Excude whole libs when building w32 dlls with -export-all

2002-04-27 Thread Robert Collins
-Original Message- From: Danny Smith [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 27, 2002 5:48 PM To: binutils Cc: cygwin-apps Subject: Excude whole libs when building w32 dlls with -export-all The auto-export feature of ld for pe-dll targets would be more flexible

Re: Excude whole libs when building w32 dlls with -export-all

2002-04-27 Thread Charles Wilson
Robert Collins wrote: Can we detect libs and automatically exclude symbols from shared libraries? i.e. when linking against libcygwin.a, ALL symbols therein are from a dll, so -by default- should not be exported. Picky point: that's not true in this case. libcygwin.a, unlike most

RE: Excude whole libs when building w32 dlls with -export-all

2002-04-27 Thread Robert Collins
-Original Message- From: Robert Collins Sent: Sunday, April 28, 2002 3:36 AM Yeah well :}. Actually most import libs can be considered to contain code - that's what the standard stub is. The Oops. The standar=d stub *used* to be. *blush*. Rob