Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Date: Mon, 16 Oct 2000 19:10:56 -0400
Message-Id: <200010162310.TAA14240@envy.delorie.com>
From: DJ Delorie <dj@delorie.com>
To: venkat@comit.com
CC: cygwin@sourceware.cygnus.com
In-reply-to: <14827.35638.551000.788842@gargle.gargle.HOWL> (message from
	Venkat Iyer on Mon, 16 Oct 2000 16:11:50 -0700 (Pacific Daylight
	Time))
Subject: Re: Solution: Exporting symbols from an executable
References:  <14827.35638.551000.788842@gargle.gargle.HOWL>


Discussions of linker changes should go to binutils@sources.redhat.com

> 1. a command line option? 

Yup.  Unless you can automatically detect when exports exist, which
might be a good automatic feature.

> 2. in the code, where the default for a dll is to export everything,
>    for an exe is to export nothing, and if there are explicit def files
>    (or dllexports) then just do whatever is specified?

Sounds good.  Look in ld/emultempl/pe.em for where the functions are
called, and ld/pe-dll.c where they are implemented.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com