Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <001d01c0dba4$c87b09c0$c5823bd5@dima> From: "Dmitry Timoshkov" To: "Danny Smith" Cc: References: <20010512025148.2365.qmail@web6402.mail.yahoo.com> Subject: Re: Linking with "stdcall" library Date: Sun, 13 May 2001 20:02:51 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 "Danny Smith" wrote: > -- start of test-dll.def -- > EXPORTS > MyCloseHandle@4 > -- end of test-dll.def -- > > > dlltool --kill-at --input-def test-dll.def --output-lib libtest-dll.a I faced with new problem arranging my build environment. The above solution provides a way to create correct import library using .def file with exported names with stdcall naming convention. But the same .def file can't be used to create the library (.dll) itself using dllwrap: dllwrap --kill-at --dllname test-dll.dll --def test-dll.def test-dll.o Resulting exported names in the created .dll have @XX suffix. Do I have to have TWO DIFFERENT .def files? One for creating import library, and another for creating .dll? Thanks in advance. -- Dmitry. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple