|
There is a gotch here: If there is a build step test for the child step it is parsed whether the "include in build" step is checked or not (on either the parent or the child). The result of this is that if the test references macros, or has side effects, things are likely to go pear shaped.
A work around is to put the child steps in a subroutine. That way they don't get looked at at all if the calling step is not included in the build.
|