Hello Roger,
Thinking about this again, I wonder if we're looking at this
correctly. What DLLs will OSG try to load using LoadLibrary? Normally,
only plugins will need to be loaded that way, because the "normal" OSG
libraries (osg.dll, osgViewer.dll, etc.) will not be loaded
dynamically, but will be loaded at program start because the program
was linked to their import library counterparts. Is that correct?
If that's the case, you need to remember that the plugins are in a
subdirectory osgPlugins-<version>, which should *never* be on the
PATH. Therefore, the OS's default search behaviour will always fail
anyways. The only way to find the plugins is to specifically add
osgPlugins-<version> to the directories in the PATH until you find one
that contains the plugin you want.
So I think the current behaviour should not be changed. Unless the
current behaviour does not check ".\osgPlugins-<version>". In that
case it should be added as the first place that is checked, before any
directories in the PATH.
The solution to the problem in your original post is to remove any
...\osgPlugins-<version> directories in your PATH. Once that's done,
your application should check ".\osgPlugins-<version>" first, and will
find the correct version of the plugins there (if you put them there,
which you should).
Hope that helps,
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
