Allow the build directory of rmm to be used for find_package(rmm)
#698
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.
This folds into the rework for libcudf to support export targets ( rapidsai/cudf#7107 ).
Developers that are iterating on
rmm
andcudf
should be ablecudf
against a local build ofrmm
without having to re-installrmm
each time they change a rmm header. This MR supports this use-case by allowingfind_package(rmm)
to work with armm
build directory.To verify this ( using rapidsai/cudf#7107 ) the following will make sure
cudf
detects your localrmm
instead of fetching it viaCPM
.