Build variants

From: Paul Schmidt (prs_at_[hidden])
Date: 2003-07-21 14:06:34

This is regarding building top-level binaries for either EE or IOP
processors on the Playstation2.

To clarify, I have a hierarchy:

test
iop
foo
ee
init
hello

I want the "foo" project built using IOP-specific include and library
paths, different link command files, and possibly completely different
build tools from the "init" and "hello" EE-specific targets. And I
want them built with a single invocation of bjam, e.g.

bjam -s"TOOLS=snps2" -s"BUILD=debug <instruction-set>*"

Demanding, aren't I? :-)

--- In jamboost_at_[hidden], Rene Rivera <grafik666_at_r...> wrote:
> In the tools file you add something like what the gcc-tools.jam does:
> 
> flags snps HDRS <instruction-set>ee : $(SCE)\\EE\\INCLUDE ;
> flags snps HDRS <instruction-set>iop : $(SCE)\\IOP\\INCLUDE ;
> 
> AND, you modify features.jam to add "ee" and "iop" as valid values
for the
> instruction-set feature.

Ok, I've done that, and test-built my mini hierarchy for the ee. What
it does, of course, is to add yet another level in the bin hierarchy,
which I can live with if it's the only way to do it - but can I
eliminate that extra level? Any given binary will be build either for
the ee or the iop, never both, so there's no reason for the extra
level of subdirectory. 

In any case, I see how to set variables based on the instruction-set,
but I'm still unclear as to how to trigger one or the other in a
particular subinclude, e.g. if I write:

subinclude <instruction-set>iop somedir ;

somedir is still built even if my command line is:

bjam -s"TOOLS=snps2" -s"BUILD=debug <instruction-set>ee" -d2 > out

OTOH, if I can put an "<instruction-set>ee" somewhere in the subdir's
jamfile:

subproject ee/init ;
lib init : init.c ;

I can live with that, too.

Suggestions?