Skip to content

Conversation

@smaslov-intel
Copy link
Contributor

No description provided.

@smaslov-intel smaslov-intel requested a review from a team as a code owner May 10, 2023 01:41
@smaslov-intel smaslov-intel temporarily deployed to aws May 10, 2023 03:38 — with GitHub Actions Inactive
@smaslov-intel smaslov-intel temporarily deployed to aws May 10, 2023 04:36 — with GitHub Actions Inactive
mkdir build-e2e
set PATH=%GITHUB_WORKSPACE%\install\bin;%PATH%
cmake -GNinja -B build-e2e -S.\llvm\sycl\test-e2e -DSYCL_TEST_E2E_TARGETS="${{ inputs.targets }}" -DCMAKE_CXX_COMPILER="clang++" -DLLVM_LIT="..\llvm\llvm\utils\lit\lit.py" ${{ inputs.cmake_args }}
cmake -GNinja -B build-e2e -S.\llvm\sycl\test-e2e -DSYCL_TEST_E2E_TARGETS="${{ inputs.targets }}" -DCMAKE_CXX_COMPILER="clang++" -DLEVEL_ZERO_LIBS_DIR="D:\github\level-zero_win-sdk\lib" -DLLVM_LIT="..\llvm\llvm\utils\lit\lit.py" ${{ inputs.cmake_args }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I'm not familiar with this macro. Doesn't this tell the test suite where to find the L0 Dev kit? Why would the L0 devkit be at this location?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, since we do not want to install the L0 loader, we require end-users install it themselves (same way we require L0 drivers). The path I used is where our Windows CI had been configured to have the L0 loader in.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I am closing this PR in favor of #9166 carrying the same change.

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