Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 15 Feb 2001 13:16:48 -0500 Message-Id: <200102151816.NAA32134@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: cygwin-developers AT cygwin DOT com In-reply-to: <20010215121332.H3899@redhat.com> (message from Christopher Faylor on Thu, 15 Feb 2001 12:13:32 -0500) Subject: Re: Exporting symbols from a .exe References: <20010215013211 DOT A2451 AT redhat DOT com> <200102151541 DOT KAA30990 AT envy DOT delorie DOT com> <20010215121332 DOT H3899 AT redhat DOT com> > With MSVC you don't have to do anything special. If I try --shared, the > executable just doesn't work. Right, because you just created a dll ;-) What I meant is that if you use the built-in mechanism to export symbols, rather than dlltool, I suspect that ld will simply not bother to check for symbols to export if you're not building a dll.