On 1/17/03 at 12:33 PM Michael Selig wrote: >At 1/17/03, Benjamin Lee Solosy wrote: >>In summary, a reasonable/working set of configure options might be: >>./configure --with-network-olk --with-weathercm >>--with-plib=/usr/include/plib >>--with-metakit=/usr/local/src/SimGear-0.3.1/src-libs/metakit-2.4.3 >>--with-simgear=/usr/local/src/SimGear-0.3.1/simgear >>--prefix=/usr/local/FlightGear --disable-jsbsim --disable-yasim >>--disable-larcsim --disable-uiuc > >Why disable the fdms (one, some, or all)? > >Also, I did not think that these disable options were part of the cvs. I >thought all discussions on this pointed to not including such >"features". If there are problems w/ compiling certain parts of fgfs on a
>particular platform, I think the developers should fix those parts rather >than simply disabling them. > >I think all of the fdms have their particular good features and associated >aircraft, and I would not want to see some or all of those die by first >disabling them and then ultimately not supporting them. > >Regards, >Michael I'm pretty sure that none of those disable-fdm options actually do anything - its probably a rare case of an open-source project where the documenters are ahead of the coders :-) As for Benjamin's suggested options, I would suggest that in a manual aimed at beginners to Flightgear - Forget --with-network-olk - its not being maintained, probably doesn't work anymore (based on a posting on the lists a while back), never worked on windows, and others (ace project) seem to be making good progress in this area. Just use the default. Why --with-weathercm - why not just forget specifying which weather module to use and just run with the default, which at the moment is FGNewEnvironment. (No offence intended to weathercm here BTW - I'm just looking at this from a 1st time compiler's perspective.) And why would anyone (especially a beginner) want to disable all the fdm's? (ignoring the fact that these options don't do anything!) In summary, I'd suggest just leaving it at the --with-metakit= --with-simgear= --with-plib= --prefix= options *if* needed/wanted, and possibly adding a mention of --without-logging which will cut down the console output a lot (and is also a valid option to SimGear's configure script, which also puts out console output). Its probably also worth stressing that if in doubt, just typing ./configure *should* work, with the possible exception of picking up the Metakit libraries. Cheers - Dave _______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users
