Implemented support for non-standard installation of oneAPI compiler by dpctl#481
Implemented support for non-standard installation of oneAPI compiler by dpctl#481oleksandr-pavlyk merged 1 commit intomasterfrom
Conversation
|
@oleksandr-pavlyk I do not like the approach of checking the compiler string. Just checking |
Ok, I will implement that, but the only difference would be that we would not insist on 2021.2 minimum version requirement. |
|
Confirmed that |
|
LGTM. In @AndresGuzman-Ballen's case all he needs to do is pass in |
|
Yes, and he already got this working on Linux, and Windows (a test fails here, but building process works) |
diptorupd
left a comment
There was a problem hiding this comment.
Please squash and merge
|
@oleksandr-pavlyk please update the docs in a follow up or as a separate commit in this PR. |
Renamed DPCTL_CSTOME_DPCPP_INSATLL_DIR to DPCTL_DPCPP_HOME_DIR, and added DPCTL_DPCPP_FROM_ONEAPI and improved their CMake description strings. We now always pass DPCTL_DPCPP_HOME_DIR to cmake when building backend. We rely on user supplied `DPCTL_DPCPP_FROM_ONEAPI` to either require minimum version of 2021.2.0, or not. The logic for querying compiler for the version got simplified. We always execute ``clang++ --version``
b9bc8c4 to
5c138ad
Compare
Closes #480
@AndresGuzman-Ballen Please check to see if this changes unblocks the use of DPC++ installation in Python environment.