Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Tor Lillqvist MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14211.57334.420000.479849@tippen> Date: Thu, 8 Jul 1999 02:17:10 +0300 (FLE Daylight Time) To: DJ Delorie Cc: cygwin@sourceware.cygnus.com Subject: Re: How can I get a .dll to resolve at runtime ? In-Reply-To: <199907072246.SAA07598@indy.delorie.com> References: <3783C923.C7742C50@olf.com> <199907072246.SAA07598@indy.delorie.com> X-Mailer: VM 6.62 under Emacs 19.34.6 DJ Delorie writes: > One thing to try is to export the function with a .DEF file, and see > if that works. You'd have to build an import library for your > executable and link the dll against that, but I'm not sure if NT would > even *allow* such a hack. Yes, it works quite well (on Win9x at least). You can specify a .def file when building an .exe with CL (or LINK), and it produces an import .LIB. With gcc -mno-cygwin it's quite a bit more convoluted, but it's possible. I came to the conclusion that with gcc you must mark the exported functions with __declspec(dllexport), the .def file is ignored. (And you must do the dance with multiple gcc and dlltool passes.) I might be wrong... --tml -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com