Hi Allen,
On Wed, 2006-07-05 at 08:58 -0500, Allen Bierbaum wrote:
> Understood.
>
> One question though. It seems that this is being removed because
> someone could compile against GLX 1.4 and then try to run with GLX 1.3.
> Wouldn't that be considered an error? I mean if someone compiled
> against version 2.0 of a library and then ran with version 1.1 of the
> library would we really say the OpenSG code is at fault for thinking
> that the library include the symbols that were detected and used at
> compile time?
That's a perfectly logical way of looking at the problem. Unfortunately,
practice usually isn't. :-/ OpenGL's highly dynamic way of handling
extensions is designed to work around this (primarily to handle
different drivers and features, but different library versions are
another option), but in this case I don't see a way to make it work, as
the name has to be defined at compile time.
> IMHO I think GV's idea of adding a configure flag seems a little more
> reasonable of a solution to this problem.
Honestly I think the bug is that glx is not loaded before OSGSystem is,
even though glx is in OSGSystsm's dependency list. Either our build
system is missing a flag, or it's a bug in the dynamic linker, but in
either case I don't think this should be a user problem.
Dirk
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
