Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42C53387.9080609@familiehaase.de> Date: Fri, 01 Jul 2005 14:13:59 +0200 From: "Gerrit P. Haase" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: undefined reference to `_CAPI_INSTALLED AT 0', why? References: <42C52EA6 DOT 5090300 AT familiehaase DOT de> In-Reply-To: <42C52EA6.5090300@familiehaase.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Gerrit P. Haase wrote: > Dave, > >>> So why does the compiler creats a reference to _CAPI_INSTALLED AT 0 or >>> is it the linker who wants to resolve CAPI_INSTALLED with @0 attached. >> >> >> >> Has the definition of APIENTRY has changed between the mfr's build from >> which the import library came and the build from which you generated your >> import lib? > > > Many thanks, that is it: > > # define APIENTRY __attribute__((stdcall)) > > How do I create an import library with stdcall convention now? > > Simply adding --add-stdcall-alias flag for dlltool seems to have no > effect. It is not really needed to edit the .def file manually? Is it? Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/