-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add support for modular build structure. #773
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Depending on the scanning regex rules it's possible to end up with empty names to try and scan for headers. Which leads to errors of trying to open such non-existent files. This avoids such errors by skipping the scanning attempt.
…torg#362) 1. Require that the directive is at the beginning of a line, sans leading spaces. 2. Require that the header name is not empty. This eliminates majority of comments that look like #include directives. One practical example is a comment in Boost.Wave that has "#include <>" and "#include """ in its body.
This expands out the failed and skipped summary tail lines to also include a sorted list of action and targets of the corresponding failed and skipped targets. This makes it easier to see them and to further search for individual ones in teh rest of the output. It also makes it possible to quickly retry specific targets. fixes boostorg#196
Adds run-flags feature to allow more control on how MPI run targets are executed. This also removes the Boost specific dependency in the `mpi-test` rule.
This adds matching of projects that are found directly with the project-search rule.
…rd slashes (boostorg#361) * src/tools/gcc.jam: Add missing :T for target file paths in linker invocation rules. This fixes builds when b2 uses a response file instead of the command line after a size limit is reached. Co-authored-by: Christian Seiler <c.seiler@luxflux.de>
As per the patch put forward in boostorg#453
Thank you for your contributions. Main development of B2 has moved to https://github.com/bfgroup/b2 Please consider following up at https://github.com/bfgroup/b2/pulls |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: