* Robert Osfield -- Monday 09 February 2009: > How easy is it to build FlightGear these days?
Shouldn't be too hard for you, as you probably have a lot of the necessary components installed already (osg, libpng, libjpg, openal, alut etc.) So all you'll need is a decent scene graph lib: ;-) $ svn co https://plib.svn.sourceforge.net/svnroot/plib/trunk plib We still use some parts of that -- networking, joystick, GUI. Then you need SimGear: $ cvs -d :pserver:cvsgu...@cvs.simgear.org:/var/cvs/SimGear-0.3 login CVS passwd: guest $ cvs -d :pserver:cvsgu...@cvs.simgear.org:/var/cvs/SimGear-0.3 co source And FlightGear itself: $ cvs -d :pserver:cvsgu...@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login CVS passwd: guest $ cvs -d :pserver:cvsgu...@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source It's the usual ./autogen.sh && ./configure && make && sudo make install everywhere, IIRC. > At my end I do have the helgrind output that suggests a problem, but I > don't have a crash, [...] I cannot reproduce the crash every time either. Happens once in a while, but *if* it happens, then the origin is always the same. There's nothing fuzzy about it. > I am looking into ways of refactoring this class to fix the potential > problems. That sounds much too dangerous shortly before a release. I'd rather look into that afterwards. Crashes aren't nice, but messing up a lib before a release is far worse. :-) > Are you around for the rest of the day? Can I push a testing question > of new code in your direction? Yes, and sure. But note that I can't reproduce it with every fgfs run. I'd have to run fgfs dozens of times and "hope" that it segfaults. m. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
