-
-
Notifications
You must be signed in to change notification settings - Fork 54
Add support for modular build structure. #183
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
Merged
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
4c33390
Make the library modular usable.
grafikrobot c66a3d3
Switch to library requirements instead of source. As source puts extr…
grafikrobot 1ad30e5
Sync from upstream.
grafikrobot 1525dc1
Add missing NO_LIB usage requirements.
grafikrobot 5c126f3
Sync from upstream.
grafikrobot a4d7bd2
Add missing use dep for building the file_test_helpers lib.
grafikrobot 214aa10
Sync from upstream.
grafikrobot 3d7e61b
Add missing import-search for cconfig/predef checks.
grafikrobot 1fe9102
Add requires-b2 check to top-level build file.
grafikrobot 0b38173
Sync from upstream.
grafikrobot cfa8548
Bump B2 require to 5.2
grafikrobot 44fb92d
Update copyright dates.
grafikrobot c548d0c
Move inter-lib dependencies to a project variable and into the build …
grafikrobot 02e9a8f
The custom feature(s) need to be at the root as they need to be defin…
grafikrobot 756e3dc
Sync from upstream.
grafikrobot efdb80f
Sync from upstream.
grafikrobot ef9415c
Sync from upstream.
grafikrobot 4514459
Remove not needed filsystem dependency.
grafikrobot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| # Copyright René Ferdinand Rivera Morell 2023-2024 | ||
| # Distributed under the Boost Software License, Version 1.0. | ||
| # (See accompanying file LICENSE_1_0.txt or copy at | ||
| # http://www.boost.org/LICENSE_1_0.txt) | ||
|
|
||
| require-b2 5.2 ; | ||
|
|
||
| import feature ; | ||
|
|
||
| feature.feature boost.nowide.lfs : auto no : optional propagated ; | ||
|
|
||
| constant boost_dependencies : | ||
| /boost/config//boost_config | ||
| ; | ||
|
|
||
| project /boost/nowide | ||
| : common-requirements | ||
| <include>include | ||
| ; | ||
|
|
||
| explicit | ||
| [ alias boost_nowide : build//boost_nowide ] | ||
| [ alias all : boost_nowide test ] | ||
| ; | ||
|
|
||
| call-if : boost-library nowide | ||
| : install boost_nowide | ||
| ; | ||
|
|
||
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason for the variable instead of inlining in build/Jamfile?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reason is to advertise the dependencies to others consistently for both buildable and header only libs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So that's intended for ("others"=)humans, isn't it? Because otherwise I don't see how this is consistent with e.g. https://github.com/boostorg/variant2/blob/a4b167b7238781d75df5d6684c9e9d40b26456dc/build.jam#L17 given that are different files
My hesitation is because now when reading/editing the build/Jamfile I need to switch to this to see the definition of a variable used there. For head-only libs it is defined and used in the same file (as the build-Jamfile doesn't exist)
To be clear: I'm not saying this is bad, I just want to understand the motivation why.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's mainly for people reading the file. I understand the concern though. The attempt is to make this uniform for all libraries (it was easier to generate all of this info this way also).