Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <39496A88.A9531612@carlthompson.net>
Date: Thu, 15 Jun 2000 16:45:12 -0700
From: Carl Thompson <cet@carlthompson.net>
MIME-Version: 1.0
To: Charles Wilson <cwilson@ece.gatech.edu>
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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...

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

> --Chuck

Carl Thompson

> ...

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