A pattern I've used in our build is to always compile everything from a common root for the following reasons (among others):
* the compiler embeds a partially qualified path into the source, making it easy to tell the debugger to look in one common root for all source files * it discourages the use of relative paths as in the following (discouraging this has helped with refactoring efforts): * *-I*../lib * #include "../lib/whatever.h" * warnings/errors in build logs will always have partially qualified paths * when printing error messages from code a simple *printf( "%s:%d: error msg", __FILE__, __LINE__ );* suffices These and other "features" not mentioned all help make it easier to refactor various projects. The project comprises over 5,000 source files and about 1.5 million lines of code. If nothing else, the relative pathing for the debugger is a must-have. How can I get tup to build from a common root (that is, not switch directories to where each tupfile is)? -brian -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
