Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <39496E2A.E3330B40@ece.gatech.edu>
Date: Thu, 15 Jun 2000 20:00:42 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: Carl Thompson <cet@carlthompson.net>
CC: Cygwin List <cygwin@sourceware.cygnus.com>
Subject: Re: Can't build a DLL using gcc
References: <852568FF.007476F8.00@D51MTA04.pok.ibm.com> <39495C96.D14912FA@carlthompson.net> <39496405.2B9FD3A@ece.gatech.edu> <39496A88.A9531612@carlthompson.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Carl Thompson wrote:
> 
> Charles Wilson wrote:
> 
> > ...
> 
> > You probably *should* use def files if (a) you're developing a library
> > that other folks might want to use, without recompiling their
> > application code, and (b) you want to support those apps that
> > 'import-by-number' from the dll. With the no-def-file method, you're
> > never guaranteed that the name/numbers will be the same from build to
> > build.
> 
> I understand what you are saying, but if developers are using my headers and
> my import library to link with my DLL, wouldn't they always be importing by
> name?  I don't know anything about the import by number method.  Why is it
> ever used?  How is it used?  More info, please...

I'm not really clear on the details -- I was reading the
libpng-developers mailing list and they were discussing the relative
merits of def-files, harvesting function names, 'export ordinals' and
'implicit' (by-number) linking. See
ftp://swrinde.nde.swri.edu/pub/png-group/archives/png-implement.0005

> 
> Anyway, I hope at least the information in my message about the alternate
> way to build DLLs helped you.

Sure -- more information is always good.

--Chuck

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