John Wojnaroski writes: > Sometimes I have trouble with "gcc -c hello.cpp"; a nice clean simple > understandable build package that I can dissect if I chose without having to > envoke mystical incantations to decipher would be appreciated.
Automake/autoconf really isn't that bad once you get going with it. There is some magic buried at the lower levels, but once you get the hang of things, it is very straight forward to debug problems and use in general. It creates a complex build system from simple input files, but most people get hung up thinking that they have to look in the configure script or in the makefiles. That's the last place you want to go (although it can be useful to debug some problems.) The trick is to realize which files you are supposed to edit and which files are autogenerated. Then the system starts to make a lot more sense. It's really just a series of macros that translates the simple input files into the complex build system we know and love. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
