Skip to content
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

rapids_export now handles explicit version values of 0 correctly #174

Conversation

robertmaynard
Copy link
Contributor

The previous logic didn't work as CMake evaluates 0 as FALSE when it comes to if statements, and therefore we didn't
build the correct version strings when a value was just 0.

The previous logic didn't work as CMake evaluates `0` as
FALSE when it comes to `if` statements, and therefore we didn't
build the correct version strings when a value was just `0`.
@robertmaynard robertmaynard added bug Something isn't working non-breaking Introduces a non-breaking change ! - Hotfix Hotfix is a bug that affects the majority of users for which there is no reasonable workaround 3 - Ready for Review Ready for review by team labels Mar 23, 2022
@robertmaynard
Copy link
Contributor Author

@trxcllnt This should resolve the issue with cuspatial at GTest

@trxcllnt
Copy link
Contributor

@gpucibot merge

@rapids-bot rapids-bot bot merged commit 7f24b28 into rapidsai:branch-22.04 Mar 23, 2022
@robertmaynard robertmaynard deleted the bug/handle_explicit_zero_version_values branch May 27, 2022 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Ready for Review Ready for review by team ! - Hotfix Hotfix is a bug that affects the majority of users for which there is no reasonable workaround bug Something isn't working non-breaking Introduces a non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants