Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Venkat Iyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14827.35638.551000.788842@gargle.gargle.HOWL> Date: Mon, 16 Oct 2000 16:11:50 -0700 (Pacific Daylight Time) To: DJ Delorie Cc: venkat@comit.com, cygwin@sourceware.cygnus.com Subject: Re: Solution: Exporting symbols from an executable > > The main thing I was missing is that you HAVE to create a .exp file. > > Since most other dlltool functionality is subsumed by ld, I wonder why > > this isn't. Or if there's some option that I couldn't figure out. > > Setting up the exports is only done when building a dll (--shared). I > don't see why it couldn't be enabled for all cases, but usually exe's > don't need one. (Disclaimer: ) I haven't studied spec files, so I don't know much about option processing. But if I were to add setting up exports even when doing an exe, would that be done as 1. a command line option? 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? -- Regards _______________________________________________________________________ Venkat Iyer venkat@comit.com Phone: 1-408-988-2988 x 136 Comit Systems, Inc. The Contract Engineering Company www.comit.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com