On 1/18/06, * * <[EMAIL PROTECTED]> wrote: > On 1/18/06, Eric Lilja wrote:
Uuggh! Sorry about the e-mail address AGAIN! Nothing like realizing .17 seconds after hitting send. > > 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 [EMAIL PROTECTED] > > >>>> 00000000 T [EMAIL PROTECTED] > > >>> > > >>> 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/
