just a little follow-up to confirm that I was able to build boost.python
stand-alone by cloning the boost.jam file into the boost.python toplevel
directory and making some minor adjustments to the build files (adding a
Jamroot, and making minor changes to the "tag" rule in Jamfile.v2).
Obviously, this can't be the real solution, so the next question is what
to aim for in terms of package dependency. If boost.jam can't be part of
perhaps there could be a boost core module
containing hat file (together with some "core headers"), which all other
boost libraries may then depend on.
Also, is there a way to support both this new modular build use-case as
well as the original integrated build ? While I have modified the build
logic in my local clone of boost.python, it would be best if I could
push those changes upstream, without breaking the existing build workflow.