Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

compnerd
Copy link
Member

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.

@compnerd
Copy link
Member Author

@swift-ci please test

@compnerd
Copy link
Member Author

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.
@compnerd
Copy link
Member Author

@swift-ci please test

@jmschonfeld
Copy link
Contributor

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?

@jmschonfeld
Copy link
Contributor

@swift-ci please test

@compnerd
Copy link
Member Author

Seems that the Linux toolchain build did uncover something. Will take a look once I clear up some more of the Windows patches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants