Add support for modular build structure.#44
Conversation
…a source in install targets.
|
Are these dependencies actually required? I see nothing in the PR that depends on them. Conversely, doesn't it depend on the PRs for the library dependencies being merged first? Where does e.g. |
According to https://pdimov.github.io/boostdep-report/develop/variant2.html yes.
Those get created by the boost-root/jamroot as needed until the transition is fully complete. Although I missed some cases that I'll need to fix. But that was the point of creating all the PRs. To shake out all the issues. |
I meant the PR dependencies listed above: boostorg/boost#854 Why would this PR depend on the tools? It seems to work as-is. |
It may well not depend on them. But I can't guarantee that building docs will work for any particular library without the tools first. As most libraries do not check if their docs build in CI. |
|
I don't think that (It currently does, but it shouldn't.) |
|
Please review and merge this PR at your earliest convenience. |
This is part of the effort to make the Boost libraries "modular" for build and consumption. See https://lists.boost.org/Archives/boost/2024/01/255704.php and https://github.com/grafikrobot/boost-b2-modular/blob/b2-modular/README.adoc for more information.
This PR depends on the following other PRs being merged to both develop and master branches of the respective repos:
This PR will be changed to ready for review, i.e. not draft, when the above are merged. Do not merge this one until that time.