X-Spam-Check-By: sourceware.org Message-ID: <2e59e6970601181742i4a7ab920l4a689ec103decbc0@mail.gmail.com> Date: Wed, 18 Jan 2006 19:42:36 -0600 From: * * To: cygwin@cygwin.com Subject: Re: Using VC-compiled Mesa binaries under Cygwin In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k0J1gjt4002268 On 1/18/06, Eric Lilja wrote: > 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@0 > >>>> 00000000 T _glutPostRedisplay@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. You placed the linker options before the library name, right? And placed the library filename on the linker command line or -L -l? How are you exporting functions in the DLL? Using __declspec(dllexport), or a .def file? How about using the .def file you developed to link the DLL. > > > > > 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/ > > -- 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/