Keith, unfortunately Eric's instructions weren't quite right :( Erik Hofman wrote: > > Just do ./configure > this will give a full list of the possibilities.
He meant ./configure --help of course :) > > Yours is: --disable-logging Actually, it is --without-logging: ./configure --without-logging (Unfortunately, "configure" silently ignores unknown options beginning with --with/without/enable/disable.) You would want to do this in both FlightGear and SimGear. But I always build with logging enabled, and then redirect to null at run time: src/Main/fgfs > /dev/null 2>&1 or to a file (because it's often useful to see what went wrong): src/Main/fgfs > ~/fgfs.out 2>&1 Both of these (to null or to a file) are fast under CygWin, whereas output to the console is slow. This is probably the main cause of your low frame rate, as long as you have enough free RAM to hold the 56MB executable. However, you can build a smaller one by omitting debugging information. There are several ways to do this. The easiest way is to strip the debugging info from the exe after it has been built: strip src/Main/fgfs.exe - Julian _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
