From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14853 invoked by alias); 1 Jul 2004 17:05:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 14836 invoked from network); 1 Jul 2004 17:05:16 -0000 Received: from unknown (HELO sauxa.salomon.at) (193.186.16.20) by sourceware.org with SMTP; 1 Jul 2004 17:05:16 -0000 Received: (from root@localhost) by sauxa.salomon.at (8.9.3 (PHNE_28760)/8.9.3) id TAA00591; Thu, 1 Jul 2004 19:05:03 +0200 (METDST) Received: from salomon.at (sapc154.salomon.at [172.28.8.78]) by sauxa.salomon.at (8.9.3 (PHNE_28760)/8.9.3) with ESMTP id TAA00566; Thu, 1 Jul 2004 19:04:51 +0200 (METDST) Message-ID: <40E44433.4090204@salomon.at> Date: Thu, 01 Jul 2004 17:05:00 -0000 From: Michael Haubenwallner User-Agent: Mozilla Thunderbird 0.5 (X11/20040601) MIME-Version: 1.0 To: cygwin@cygwin.com CC: RaoulGough@yahoo.co.uk Subject: Problems linking stdcall functions from DLL Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-11 X-SW-Source: 2004-07/txt/msg00040.txt.bz2 Some time ago, there was a question about linking third party dll's with cdecl function declarations but without the @x-decorations: http://www.cygwin.com/ml/cygwin/2003-09/msg00307.html Is there already a solution for this problem, as i've seen this test not working yet with recent binutils-20040312-1/ gcc-3.3.1-3 on cygwin-1.5.10-3 ? Would the use of LoadLibrary()/GetProcAddress() help to keep the stack valid ? Thought just to mention an interesting site i've found about this: http://mywebpage.netscape.com/yongweiwu/stdcall.htm Thanks, Michael Haubenwallner -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz mailto:michael.haubenwallner@salomon.at http://www.salomon.at -- 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/