X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Eric Lilja" <mindcooler AT gmail DOT com>
Subject:  Re: Using VC-compiled Mesa binaries under Cygwin
Date:  Wed, 18 Jan 2006 13:27:42 +0100
Lines: 33
Message-ID: <dqlc7s$2a0$1@sea.gmane.org>
References:  <dqlbd0$v34$1 AT sea DOT gmane DOT org> <SERRANOqngL6wxvw0ID000001a2 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Dave Korn wrote:
> Eric Lilja wrote:
>
>
>>>> However, doing a nm GLUT32.lib | grep glutPostRedisplay (the first
>>>> undefined reference), shows: $ nm GLUT32.lib | grep
>>>> _glutPostRedisplay 00000000 I __imp__glutPostRedisplay AT 0
>>>> 00000000 T _glutPostRedisplay AT 0
>>>
>>> This is definitely the MSVC name mangling convention.... but I think
>>> that gcc doesn't append the number of bytes on the end.  What
>>> calling convention did you compile with?  I think MSVC adds the
>>> argument size to stdcall but not cdecl, or else the other way
>>> around.
>>
>> I checked the glut project and it's built with __cdecl by default. I
>> changed to stdcall,
>
>  I think what you really want to be doing is investigating the linker
> option "--enable-stdcall-fixup" and perhaps adding it to the linker
> command line?
>

Since posting, I've reverted to cdecl-variant of glut (the default), and 
adding that linker option when using the raw dll (i.e., no pexports/dlltool 
generated files involved) yields the same linker errors as before. =( Maybe 
I misunderstood you. Thanks for trying to help.

>
>    cheers,
>      DaveK 




--
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/