2 questions:
1. Are there cross compiling resources for bbv2 out there?
It appears
gcc.jam is not cross compile capable, but it would probably
not be hard to
create a variant that would. Is this the
"correct" approach to cross
compiling, that is, creating a new bb toolset?
2. Say you want to cross compile the Python package. The
package consists
of the python interpreter plus a collections of libraries.
The libraries
require the python interpreter for construction. This is
fine when not
cross compiling, but when cross compiling the cross python
will not run on
the build system.
Ideally you would want to specify a non-cross python
interpreter as a
dependency of the libraries, but I haven't seen anything in
the
documentation about adding tool requirements to specific
targets. The holy
grail is to express the build instructions so that it works
nicely in both
cross and non-cross situations; ie, a non-cross compile
would construct
build-python and build-libs, where a cross compile would
construct
build-python, target-python, and target-libs.
Can bbv2 hack this?
I'm actually fooling around with Erlang, but Erlang and
Python share the
same cross build problems.
Thanks,
Dan.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|