I need support for the following scenario:

There is a complex application which consists of
multiple parts represented by separate projects
with interproject build dependencies between them.

There are two ways to build the whole application
(way A and way B) and each of the parts has to be
built in the appropriate way (A or B) for it. I
can imagine setting up a separate tree of build
dependecies for building in way A and way B, but
in my scenario the dependencies will be exactly
the same, as well as all the parameters of all
build steps. 

It would be convenient if I could design all my
build steps to support two ways of compiling (A/B)
and pass a parameter around to specify what
compilation is needed. The whole application would
use the parameter to control how the parts are
built. There would be a default for what to do
when there is no parameter (e.g. Build action on
the build step for the individual parts of
application).

Any suggestions for how to solve this?