Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <39496A88.A9531612@carlthompson.net> Date: Thu, 15 Jun 2000 16:45:12 -0700 From: Carl Thompson X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) MIME-Version: 1.0 To: Charles Wilson Cc: Cygwin List Subject: Re: Can't build a DLL using gcc References: <852568FF DOT 007476F8 DOT 00 AT D51MTA04 DOT pok DOT ibm DOT com> <39495C96 DOT D14912FA AT carlthompson DOT net> <39496405 DOT 2B9FD3A AT ece DOT gatech DOT 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 AT sourceware DOT cygnus DOT com