From: Andreas Bogk (andreas_at_[hidden])
Date: 2006-04-25 07:41:45
I'm currently evaluating the usage of Boost.Build for our software
development. We have a rather intricate set of requirements for
building. I've looked at Boost.Build, and managed to set up a
hierarchical set of project decriptions that builds a simple executable,
but I've been unable to find a good approach for the following aspects
* Cross-Compilation support
This should be obvious, we need to cross-compile for a number of
embedded platforms. I know that's a feature other people need too,
what's a good way to get started?
* Mixing different compilers
We need to compile different libraries using different toolsets, and
link them all together into one executable. It's not clear to me how
this can be done.
* Separate build directories
I might want to compile for different embedded devices, which are
all the same nominal platform (WinCE), but require a different set of
<define>s. How do I express that, and how do I keep the build results
for different sets of <define>s apart?
It would be nice if somebody could give me a few hints there on how to
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