Skip to content

Add support for modular build structure. #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 30 commits into
base: develop
Choose a base branch
from

Conversation

grafikrobot
Copy link
Member

@grafikrobot grafikrobot commented Jul 20, 2024

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.

@grafikrobot grafikrobot marked this pull request as ready for review August 18, 2024 15:16
@grafikrobot
Copy link
Member Author

Please review and merge this PR at your earliest convenience.

@grafikrobot grafikrobot closed this Apr 5, 2025
@grafikrobot grafikrobot reopened this Apr 5, 2025
@pdimov
Copy link
Member

pdimov commented May 2, 2025

This changes CI to use cpp-actions, which has nothing to do with modularity and should be a separate PR (which I'm not going to merge.)

@grafikrobot
Copy link
Member Author

It was the only way I could get the tests to pass. If you are willing to merge this without the tests passing I can undo the CI changes.

@grafikrobot grafikrobot closed this Jun 5, 2025
@grafikrobot grafikrobot reopened this Jun 5, 2025
@grafikrobot grafikrobot closed this Jun 5, 2025
@grafikrobot grafikrobot reopened this Jun 5, 2025
@pdimov
Copy link
Member

pdimov commented Jun 6, 2025

Why the change from toolset: gcc-4.8 to toolset: gcc; compiler: g++-4.8? The former should work.

@grafikrobot
Copy link
Member Author

Why the change from toolset: gcc-4.8 to toolset: gcc; compiler: g++-4.8? The former should work.

IIRC one of the runs like that didn't actually work. So switched to being explicit.

@grafikrobot
Copy link
Member Author

PS. Technically it should not work. As that toolset ends up in user-config. And that should use the plain toolset names to import. The versioned gcc-x.y only works in the CLI feature spec which gets parsed and auto-initialized as given.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants