As thoughts are turning towards a release, I wanted to bring up a couple of things. This time we are depending on libraries -- OpenSceneGraph -- that are not usually built statically. They are built for dynamic linking, and libraries that implement data file loading are loaded and linked on demand according to the file extension of the loaded model. OpenSceneGraph can be linked statically, but this seems to cause people problems -- from what I can see on the osg-users mailing list -- and would lose some of the model-loading flexibility we get for free with OSG. So, I recommend we ship the dynamically linked libraries with our binary releases and resign ourselves to doing what's necessary to make this work when FlightGear is installed. On Linux, I think it is easiest to have a front-end script that will set the proper library path to pick up these libraries.
On Linux you might think that we could blow this off and depend on the distributions' OpenSceneGraph package, but this is not practical. OpenSceneGraph releases come fast and furious; we will be depending on OSG 2.8, and (for example) my distribution of choice is still supplying 2.2. So we need to supply to proper version. I'm happy to punt Windows and Mac issues to people who are knowledgeable about that. For Linux, should we try to build a binary release to an LSB standard? http://ldn.linuxfoundation.org/lsb Thanks, Tim ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
