I salute the switch to the Makefile, even if it's a pain. It makes a LOT of sense to keep all the details of a compilation (commands, switches, command-line variables, etc.) in one text file which can be controlled by a version control system.
Most IDEs keep that information in some proprietary project file that may be binary, may change from version to version and may not be readable either by humans or other IDEs. Worse, sometimes people working on one project prefer different IDEs. Here's the GNU 'make' manual: <http://www.gnu.org/software/make/manual/html_node/> -Ken Jackson Stanley Lee writes: > Sorry for the additional spam, but I have a few more questions > about the Makefile as I am on the way of switching away from > using piklab ide and more towards using the Makefile. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
