2 replies to this topic

[Nicholas Christopher]

I am calling Gl functions in a DLL that have been assigned to pointers in an EXE then passed to the DLL through a struct.

// IN EXE
tGUMIToolsSetup.____glewActiveTexture= glActiveTexture;

// IN DLL
 #define glActiveTexture  lptGUMIToolsSetup->____glewActiveTexture 

Context and GL initialization is set in the EXE.

Everything works, except texture ID's are not being respected/maintained.
What I mean here is glBindTexture, or glActiveTexture seems to fail.

When I change the view , textures are switching between one and the next.

The same code in the DLL if executed in the EXE works perfectly.

Anyone run into this problem?

[Reedbeta]

Try calling wglMakeCurrent in your DLL before your GL calls?

Also, why not just include glew in your DLL, rather than using this roundabout way of getting the GL function pointers?

[Nicholas Christopher]

Hi Reed,

You question made me ponder, and so I tried it a second time, and this time I called glewInit(); obviously in the EXE but again a second time in the DLL.

This has worked..

Thanks for the light.