-
Notifications
You must be signed in to change notification settings - Fork 32
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
use install- features instead of package module #70
Conversation
b7cf99d
to
dbef53f
Compare
dbef53f
to
fa98e51
Compare
Update: bfgroup/b2#392 makes |
Related issues: #34, #46. Both should be fixed if this and boostorg/headers#1 are merged. |
#32: while writing this PR I also wondered why DLLs aren't installed into bindir. |
They are, but only on Cygwin for some reason. Is this ready to merge at this point, replicating the old behavior 1:1? |
Should be. It does work on my machine ™️ |
To move DLLs into bindir, we'll probably have to introduce dlldir so that people have a way to get the old behavior back. |
|
Why did this stop working? The PR run passed. |
Maybe I needed to merge the headers PR as well? |
The headers PR shouldn't be necessary. I'll re-push and check. |
Ok, something else definitely broke. I'll investigate. |
The core of this change is swithcing from using the
package
module toinstall-
features. This potentially allows property-set-based install prefixes and proper staging. In addition, there's some simplification done by switching fromgenerate
targets tomake
targets. Also, all helper features are removed and<flags>
is used instead.PS-based installation and proper staging doesn't work yet because
/boost/headers//install
doesn't useinstall-
features.One note: most
install-X
features don't check corresponding--X
options. Onlyinstall-prefix
does. This is probably an oversight, so I should change that in b2 project.