-
Notifications
You must be signed in to change notification settings - Fork 188
build: adopt current best practices for installation #1212
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
base: main
Are you sure you want to change the base?
Conversation
@swift-ci please test |
This is replicating what has been done with swift-testing, swift-corelibs-xctest, and is in the process of being applied to swift-corelibs-libdispatch as well. |
Add the `*_INSTALL_NESTED_SUBDIR` option and use `-print-target-info` to compute the install locations. This reduces the number of times we need to invoke the compiler and compute these values.
@swift-ci please test |
Co-authored-by: Jeremy Schonfeld <[email protected]>
The change itself looks ok to me now - thanks for the explanations, but since this repo can't test CMake changes can you build a Linux + Windows toolchain via a cross-repo PR so that we can compare the toolchains and make sure that things still build and that they end up in the right places? |
@swift-ci please test |
Seems that the Linux toolchain build did uncover something. Will take a look once I clear up some more of the Windows patches. |
Add the
*_INSTALL_NESTED_SUBDIR
option and use-print-target-info
to compute the install locations. This reduces the number of times we need to invoke the compiler and compute these values.