Import llvmconfig using cmake module path instead of finding abs path #3199
Conversation
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
…n, just use the real native cmake target. This fixes part of the Xcode build by allowing us to avoid having to use cmake variables with an unexpanded CMAKE_CFG_INTDIR. Since those variables are not expanded, they point to a non-existant path like: .../$(CONFIGURATION)$(...)/lib So finding tablegen fails. In the cross compile case, we still try to find the native tablegen. rdar://26154980
…e, just add all of the LLVM cmake paths to the CMAKE_MODULE_PATH and just use include(LLVMConfig). rdar://26154980
|
@swift-ci Please smoke test |
gottesmm
deleted the
import_llvmconfig_using_cmake_module_path_instead_of_finding_abs_path
branch
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.
What's in this pull request?
Resolved bug number: (SR-)
Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
Validation Testing
Lint Testing
Note: Only members of the Apple organization can trigger swift-ci.