Hey everyone, I’m trying to build a plugin on Windows that I wrote, compiled, and tested on Linux. I’m using the same build environment and project configuration I always use to build Windows plugins, but I’m getting a whole lot of "unresolved external symbol" linker errors that appear to be pointing to GL functions.
1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glNewList 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glDeleteLists 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glPointSize 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glPushMatrix 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glGenLists 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glRotatef 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glPopMatrix 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glEnd 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glBegin 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glScalef 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glVertex3f 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glColor3f 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glEndList 1>Hist3D.obj : error LNK2001: unresolved external symbol __imp_glCallList This is the first plugin in which I’m directly using GL calls, so I’m curious if there is some obscure additional include I need in order to get the GL code working on Windows (other than the forced stdafx.h). Anyone have any thoughts on or experience with this kind of situation? Thanks, -Nathan
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
