still getting errors linking opengl

David Medlock noone at nowhere.com
Tue Dec 4 19:00:02 PST 2007


Still trying to make D 1.018+ link with my (formerly working) OpenGL 
code.   1.017 still works right 'out of the zip'.

It appears to not want to link in opengl32.lib.  I am using glfw 2.5 and 
its bundled OpenGL bindings with Digital Mars C libraries.

I get the usual errors when the opengl32.lib is not specified even when 
I copy the lib into my project directory directory.

Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl7glBeginFkZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl10glColor3ubFhhhZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl10glVertex3fFfffZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl5glEndFZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl9glColor3fFfffZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl12glTexImage2DFkiiiiikkPvZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl12glTexCoord2fFffZv
Z:\proj\python\build\obj\main_rel.obj(main_rel)
  Error 42: Symbol Undefined _D2gl10glVertex2fFffZv

Since the glfw header starts with:

version( Win32 ) extern(Windows):

Shouldn't those errors be C-mangled names and not D ones?

Any pointers?  Walter?

-David



More information about the Digitalmars-d mailing list