|
|
|
|
#1
09-30-2003, 03:50 PM
|
|||
|
|||
|
Common macros, script (and subroutines?)
"common" macros and script grouping would provide resources from a location shared by a number of machines. This would facilitate moving a build context from one machine to another and help people who have multiple build systems.
If "common" macros were found before "system" macros local environment variable would override "common" macros. I'm not sure if that is good or bad! 
|
|
#2
10-06-2003, 04:14 PM
|
|||
|
|||
|
One way to do this is to put your common macros and script code into the global macros/script, then add the global macros/script files to your version control system, and then retrieve and load these at the start of your build.
|
|
#3
10-06-2003, 05:01 PM
|
|||
|
|||
|
We have some macros that are Global to all projects, but Local to the machine (Mapped drives and application locations for example), and others that are common across projects independent of machines.
This is not an urgent problem. It came up when moving our build system from one machine to another and we were thinking about how to set up multiple build machines at some point in the future.
|
 |
|
|
Hybrid Mode
