-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retain the original path to Kokkos #287
Conversation
Since |
Except that this would bypass the search procedure |
Are you concerned about step 4 to step 9 as well? |
Here's my (admittedly incomplete) understanding of how things will work. Per
Thus, from this point on we will consider Per
In Module mode,
However:
So it sounds like indeed it shortcuts the search procedure. |
To further investigate it, lets see what happens when trying to build
We used a (non-existing) Now, lets see what happens when we have if(NOT DEFINED Kokkos_DIR)
set(Kokkos_DIR /home/xap/local/opt/kokkos/lib/cmake/Kokkos)
endif()
find_dependency(Kokkos) in
We see that it does not check Now, lets see what happens if we do this: find_package(Kokkos QUIET)
if(NOT Kokkos_FOUND)
set(Kokkos_DIR /home/xap/local/opt/kokkos/lib/cmake/Kokkos)
find_dependency(Kokkos)
endif() Note that the first line
This time, indeed, all search paths are exhausted before fallback |
The new patch is safe from the behavior point of view. We exhaust all |
This PR is simply to facilitate the discussion of the best approach to provide transitive path to Kokkos when using ArborX.
The current approach was taken from Cabana.
Feel free to close if you think this is useless.