And one more comment - any of the proposed methods will have a problem compared to loading global macros via /macros command-line parameter:
- /macros loads all macros in bulk and only after that starts evaluating (expanding?) them;
- on the contrary, loading macros via subproject or XML parsing requires all prerequisite macros to be loaded before their dependent macros (for macros expanding). So one must create and maintain a strict order of macros in the xml file.
So, why don't allow multiple /macros switches on command-line?
|