Hi Serge, On 5/21/07, Serge Lages <[EMAIL PROTECTED]> wrote:
Currently under Windows as the core OSG dlls are not versionned, it brings nothing to prevent mixing versions, so yes it just brings me more complexity for my custom scripts, without any benefits.
Possible no extra benefits for you since you've already got systems in place to prevent library mixing. The version naming of osgPlugins should help others. Its also important to keep the convention the same across all platforms.
It's not a big burden and for sure I can live with it, so now the real question should be how to improve it under Windows to really prevent version mixing. :)
post fixing the version onto the library name would be the obvious way of doing, but without symbolic links this does force the app developer to specifically target a particular version of the lib i.r. libosg-1.9.5.dll rather than libosg.dll. Quite a few support emails each month come through because of people installing various versions of the OSG on one system and paths picking up different ones. So if we can solve this well this issue and associated support will disappear. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
