Jon S. Berndt wrote: > Andy Ross wrote: > > Is it possible that the JSBSim from CVS builds without > > optimization and that therefore the core developers aren't aware > > how slow things are for those building from the FlightGear tree? > > This is really hard to believe. On my machine (which is a 1.2 GHz AMD > machine) I can build JSBSim in standalone mode (which includes a > compile of FGState.cpp, of course) in 90 seconds - with > properties. Something's not right on your machine, I suspect.
Try the version in FlightGear, not the standalone one. I think my theory about you guys having optimization disabled is sounding more correct. The one that gets built out of FlightGear's CVS uses the standard -O2 flag, and is dog slow. I assure you there is nothing wrong with my machine. I get the same results with gcc 2.96 (the horrid evil Red Hat version that everyone hates) and 3.0.4, when building on the local drive or over NFS. And more to the point, everything else that compiles does so in a normal manner. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
