From: Paul Schmidt (prs_at_[hidden])
Date: 2003-07-14 10:45:15
--- In jamboost_at_[hidden], Rene Rivera <grafik666_at_r...> wrote:
> The ones you are using are global variables, hence they only have
> To fix... you need to set those variables "on" the target so that
they get a
> specific different value for each target built with the corresponding
Ahhhh. So what's happening is *all* of the toolsets are loaded up
front, and the variations in the build process are dependent on the
TOOLS= argument on the command line.
Thanks very much, but this leads to another problem. For the
Playstation 2, there are actually *2* processors in the box (EE and
IOP), and although the instruction sets are (more or less) the same,
include paths and libraries are different between the two. Aside: The
binary file extensions are different, too: .ELF for the EE, and .IRX
for the IOP.
So some binaries need to be built for the EE, and some for the IOP. It
seems that creating a new toolset for the IOP side might not be the
right approach, because then e.g. a top-level
bjam -sTOOLS="snps2ee snps2iop"
will build both binaries for all subprojects, and that's not what we
What would be the right approach to for this?
Again, thanks in advance...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk