[UR] For non-standalone builds, use built DPCXX/Extractor #18062
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.
If we are not a standalone build (that is, we are built as part of
intel/llvm) and
UR_DPCXX
is not specified as part of the cmakeoptions, we use the
clang
built byintel/llvm
to generate devicebinaries.
Likewise, if no
UR_DEVICE_CODE_EXTRACTOR
is specified and we arenot standalone, the
clang-offload-extractor
from intel/llvm is used.This change should not affect CI, but does mean that the UR testing
targets can be built in an intel/llvm local build.