Hi,

If my suggestion is, at least in part, acceptable, the deployment is restricted to once per platform flavour ... c/w once per consumer/user.

The suggestion regarding the common includeable make(1) script presumes that the same build standard is required on all platform flavours.

If the standard make test install fails, then you've probably got bigger worries. Note also that, without intending to be offensive, it almost sounds like you aren't aware that...

• the test target causes a build of the whole module - including any XS elements.
• the install target is attempted iff the test succeeds.

Thus, the build is simplified ... as is the deployment and as I say, if something like the topology I suggested is employed, the amount of either is reduced.

Hope that clarifies things (a bit) ,