default install-package to Boost #77
Merged
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
grisumbras
force-pushed
the
fix/libs-wrong-package-name
branch
from
ec511cf
to
aa4ca5e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
<install-prefix>on Windows defaults toC:\<install-package>.<install-package>defaults to project's id if it has one, otherwise to the first id of an ancestor project. Before modular changes this resulted in libs/Jamfile inheriting project id of boost root (boost) and default installation prefix on Windows wasC:\boost. But with modular changes library projects have their ids, and install intoC:\<lib>instead. This change tells projects that by default they should install toC:\Boost.