[UR] Use relative xpti/xptifw source when available #17099
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
kbenzie
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
pbalcer
approved these changes
Feb 20, 2025
RossBrunton
reviewed
Feb 20, 2025
kbenzie
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
In standalone UR builds, when the relative xpti/xptifw directories exist, use those instead of using `FetchContentSparse_Declare` helper.
kbenzie
force-pushed
the
benie/ur-xpti-relative-dirs
branch
from
270a13d to
8287e9b
Compare
kbenzie
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
kbenzie
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
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.
In standalone UR builds, when the relative xpti/xptifw directories exist, use those instead of using
FetchContentSparse_Declarehelper.