Subject: [Boost-build] Native-built tools in a cross-compile environment
From: Kylo Ginsberg (kylo_at_[hidden])
Date: 2012-10-15 20:53:19
I have ported a project using boost-build from Windows (using msvc) to
Linux (using gcc), and am now porting it further to a cross-compiled
Linux (also using gcc). I want to support all 3 platforms long-term
(Windows, native Linux, cross-compiled Linux).
I've put in the basic support for cross-compilation, simply by adding
a new "using gcc ..." line. However, this project uses some
code-generating build tools which are built afresh with every build --
with my current basic support for cross-compilation, these build tools
are cross-built and thus don't run on the build machine. In short,
these need to be native built at all times and I'm not sure how best
to specify this. Is there a best practice for this scenario?
I can certainly provide more detail on the organization of the
Jamfiles, etc, but figured I'd start with a short-ish note ;>
Thanks in advance for any help!
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