Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com In-reply-to: < "292623D6B0EAD04C*/c=US/admd= /prmd=National/o=notes/ou=Americas/s=Kauffman/g=Lior/"@MHS> (Lior.Kauffman@nsc.com) Subject: Re: CYGWIN application & MSVC dll References: < "292623D6B0EAD04C*/c=US/admd= /prmd=National/o=notes/ou=Americas/s=Kauffman/g=Lior/"@MHS> Message-Id: <20020827125147.7B9263DCB@cavall.jtang.org> Date: Tue, 27 Aug 2002 08:51:47 -0400 (EDT) From: tang@jtang.org (J. Tang) > Date: 26 Aug 2002 22:31:25 -0700 > From: "Lior Kauffman" > Cc: cygwin > > is there are special guidelines for building the MSVC compiled DLL > (dlltool ?) From Visual Studio, set the project type to be a relocable library (DLL). I ended up hand-editing its .def file to list the exportable functions; for some reason __cdecl did not work for me. > how do I load the MSVC compiled DLL from the CYGWIN application (by > which command ?) I used dlltools to load the DLL at runtime; see this older mailing list post: http://cygwin.com/ml/cygwin/2002-08/msg01141.html Now if you're referring to linking to the DLL at compile time, see http://cygwin.com/cygwin-ug-net/dll.html#DLL-LINK. Note that I have not personally done this yet; I have only built and used relocatable MSVC DLLs. I've also built and used relocatable Cygwin DLLs, but gave up after this: http://cygwin.com/ml/cygwin/2002-08/msg01002.html, with a follow-up at http://cygwin.com/ml/cygwin/2002-08/msg01046.html. -- Jason Tang / tang@jtang.org / http://www.jtang.org/~tang -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/