> > > The problem is LINKING! > > Is it? Why not solve it in the same way LibGGI and its extension solve it? > > Just dynamically load a renderer lib and link that one to the lib in > > question. > That was my first thought too. However, there's a catch; If you link the > sublib with the appropriate GL library when you go to link your program > with libggigl all of the opengl symbols are missing!
Well yes, but that isn't much of a problem. I am using something similar in a module system that will use externally provided functions. You can ask the linker to shut up and link on runtime only. Ugly but works. It has some drawbacks, though, as it will mask any other functions youz have not provided, thus leading to ugly runtime errors. Another method would be to provide stubs that get redirected internally. Quite some task for a large API like OpenGL. CU, Andy -- Andreas Beck | Email : <[EMAIL PROTECTED]>
