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 content-class: urn:content-classes:message Subject: RE: Excude whole libs when building w32 dlls with -export-all MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 27 Apr 2002 19:09:51 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Danny Smith" , "binutils" Cc: "cygwin-apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3R9A2921154 > -----Original Message----- > From: Danny Smith [mailto:danny_r_smith_2001 AT yahoo DOT co DOT nz] > 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 with an option to exclude whole archive libs > from export. 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. That would remove the need for many default exclusions, and be closer to unix behaviour (as I understand it). Rob