Hello Roger,
> Please remember, that as I mentioned in my initial post, my comments
> were limited to the windows platform only.
I am working mostly on Windows as well, and I have never had a
problem. The rule is clear and easy to follow: Never put any directory
containing OSG plugins on the PATH.
If your application is finding another version of the plugins, then
there are two possibilities:
a) Your versions of the plugins weren't in the correct "osgPlugins-<version>"
subdirectory (perhaps they are in another version's directory?)
b) Their plugins were in a directory which is on the PATH.
You can easily ask your users to modify their PATH and remove any
directory that contains OSG plugin DLLs. That would solve your
problem. If that breaks other programs, that's the other program's
responsibility. As you said, you have no control over other programs
(installers or not), all you can do is make sure your own program
works and that involves removing those directories from the PATH.
Anyways, if a program wants to rely on a local version of the OSG, it
should not even modify the PATH at all.
I agree that this isn't clearly documented, and don't quite know how
to make it clearer. Quite frankly, the current Wiki is a jumble of
information, some of it refers to old versions of OSG and is not up to
date anymore... I think a complete re-read of the Wiki is needed,
perhaps by a few seasoned OSG developers.
For now, you have some solutions. Good luck,
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://whitestar02.webhop.org/
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
