Hi Ed, I believe few users have as many problems with getting models to load under unix as you have... I suspect you are trying to make things more complicated than they really should be, seemingly trying you best to break the OSG, rather than just let it gone with what it's designed to do. We can only guess what this might be as you explanation of what you have done doesn't provide enough useful information. What Paul Mart wrote might indicate an avenue that might be worth looking at.
On Thu, Mar 24, 2011 at 10:37 PM, Paul Martz <[email protected]> wrote: > I believe you have a version problem on your hand. Do you have multiple > versions of OSG on your system? The debug output indicates it's looking for > the OSG v2.9.9 FLT plugin, but you said previously you're using 2.8.3, so it > doesn't find it (no surprise). I imagine that when you add the path to > LD_LIBRARY_PATH, it *does* find it, but it finds the 2.8.3 version, which is > incompatible with the 2.9.9 version of the rest of OSG, so you get a crash. > > Bottom line is that when you have multiple versions of OSG installed, you > need to manage your PATH and LD_LIBRARY_PATH very carefully. If Paul is correct and you are getting a crash because you've linked your application to OSG-2.8.3 and then at runtime forcing the loading of the osgPlugins-2.9.9/osdb_openflight.so then you will certainly get a crash as the two different releases aren't binary compatible. Now the OSG goes to lengths to try and prevent this mixing of OSG versions - we use so version'd libraries and plugins that all site withing a version plugin directory, and on load the OSG will know which version it is and which plugin directory to look for. However, you can break this system is you force it to look in the wrong plugin directory by settings the LD_LIBRARY_PATH to point to the version plugin directory, you don't say you've done this but this is my best guess to what you are doing wrong. All you should have to do is set the LD_LIBRARY_PATH to path to the libraries, and let the OSG at runtime append the osgPlugins-version so that it can find the appropriate plugin. Now if you aren't finding the plugins if you use this approach then it suggests that you have placed the osgPlugins-version directory into the library directory as it should be. Now the OSG does have a proper install script and if you use it will place all the libraries and plugins in all the correct directories, perhaps you've bypassed this completely and are copying stuff around by hand and screwing things up. As I said we can only guess. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
