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

Statically link gtest/gbench/nvbench into all C++ test/benchmark executables #32

Closed
vyasr opened this issue Mar 26, 2024 · 2 comments
Closed
Assignees

Comments

@vyasr
Copy link
Contributor

vyasr commented Mar 26, 2024

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.

@robertmaynard
Copy link

robertmaynard commented Apr 15, 2024

PRs to resolve this issue in RAPIDS repos:

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
@robertmaynard robertmaynard self-assigned this Apr 30, 2024
@robertmaynard
Copy link

Closing as RAPIDS has been converted to static gtest/gbench/nvbench

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants