-
Notifications
You must be signed in to change notification settings - Fork 4
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
Statically link gtest/gbench/nvbench into all C++ test/benchmark executables #32
Comments
7 tasks
3 tasks
rapids-bot bot
pushed a commit
to rapidsai/ucxx
that referenced
this issue
Apr 23, 2024
Part of the effort to move all of RAPIDS over to a set of static testing / benchmarking libraries ( rapidsai/build-planning#32 ). Authors: - Robert Maynard (https://github.com/robertmaynard) Approvers: - Peter Andreas Entschev (https://github.com/pentschev) - Vyas Ramasubramani (https://github.com/vyasr) - Jake Awe (https://github.com/AyodeAwe) URL: #223
Closing as RAPIDS has been converted to static gtest/gbench/nvbench |
rapids-bot bot
pushed a commit
to rapidsai/wholegraph
that referenced
this issue
May 10, 2024
Contributes to rapidsai/build-planning#32 Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - https://github.com/damontecres - Ray Douglass (https://github.com/raydouglass) URL: #167
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we typically dynamically link gtest/gbench/nvbench into our tests/benchmarks. This is unnecessary and it makes these executables harder to consume for people who want to run our tests/benchmarks. We should change this default across RAPIDS. The first step will be updating rapids-cmake to support using gtest statically. Once that is done, we can start rolling out the changes across RAPIDS.
The text was updated successfully, but these errors were encountered: