Copy nvcomp-2.3 shared libs from the cudfjni build #239
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jim Brennan <[email protected]>
jbrennan333
force-pushed
the
jtb-nvcomp-2.3
branch
from
53878a1 to
5f28660
Compare
jlowe
approved these changes
May 12, 2022
|
rapidsai/cudf#10851 is in process of being merged, so I moved this out of draft state. |
|
build |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add support for building with the nvcomp-2.3 shared libraries release.
Most of the work for supporting nvcomp-2.3 is in related cudf PR: 10837. For spark-rapids-jni, all we have to do is copy the shared libraries from that build so they can be included in the resulting jar file.
NOTE: we should not merge this until the CUDF support is finalized. It is possible that changes on the CUDF side might require changes here as well. For this reason, I am filing this as a draft PR.