Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 21 Jul 2001 19:19:21 +0930 From: Alan Modra To: Ralf Habacker Cc: Binutils , Cygwin Subject: Re: Problems with generating kde2 dlls under cygwin Message-ID: <20010721191921.F14307@bubble.sa.bigpond.net.au> Mail-Followup-To: Ralf Habacker , Binutils , Cygwin References: <000501c111c8$13aed1c0$b06707d5 AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <000501c111c8$13aed1c0$b06707d5@BRAMSCHE>; from Ralf.Habacker@freenet.de on Sat, Jul 21, 2001 at 11:32:36AM +0200 On Sat, Jul 21, 2001 at 11:32:36AM +0200, Ralf Habacker wrote: > g++ -shared -Wl,--whole-archive -Wl,-no-whole-archive > > > and if are import libs of other shared libraries. > If contains a static lib, the used symbols of this lib are always > exported. Why do you think they should not be exported? A static lib is just an archive of object files. When object files are retrieved from a static lib to satisfy undefined syms, they are treated the same as if you had specified the individual object files on the command line. Alan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/