Hi Greg, > I go further: I > say that _all_ command-names that a makefile will issue _should_ be > "encapsulated" in predefined variables. The reason why it should be > done for all of them is the same reason why it was done for "rm -f": so > that a developer easily can accomodate the differences between different > operating systems' command-processors. The GNU make manual says the exact opposite (third section below): ========== Makefiles should provide variables for overriding certain commands, options, and so on. In particular, you should run most utility programs via variables. Thus, if you use Bison, have a variable named BISON whose default value is set with ‘BISON = bison’, and refer to it with $(BISON) whenever you need to use Bison. File management utilities such as ln, rm, mv, and so on, need not be referred to through variables in this way, since users don't need to replace them with other programs. ========== From: http://www.gnu.org/software/make/manual/make.html#Command-Variables Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Jun 2 22:49:35 2011
This archive was generated by hypermail 2.1.8 : 2011-06-02 22:49:38 CEST