On 8/10/07, Orhun Birsoy <[EMAIL PROTECTED]> wrote: > I'll first ask a question. LD_LIBRARY_PATH (DYLD_LIBRARY_PATH, PATH) > is already being used by the operating system to search for the > library. What I don't understand why OSG needs to append these to the > filename and do the search itself? Doesn't the operating system > already doing it if you provide just a filename?
As J-S explained, the OSG is using this path list to look for plugins, and these plugins will be nested in a osgPlugins-version directory, the plugin won't be in the directly in the system directories or ones pointed to directly by *LD_LIBRARY_PATH. > Just in case, it is possible to add "." (ie current directory) to > LD_LIBRARY_PATH. (ie ".:/usr/lib"). > > In my experience, OSG_LIBRARY_PATH (in > Registry::initLibraryFilePathList) is enough to customize the plugin > loading paths. This is nice for you, but... its not just a case of customizing the library path, the library paths have to be their to find the plugins even in standard locations, unless you want to advocate putting 80 plugins into /usr/lib... So after all the wasted bandwidth all it comes down to is a mis-understanding of what the library path is used for. Robert. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
