Add CUDF_USE_BENCHMARK_STATIC option to build and statically link Benchmark

[trxcllnt]

Description

Add CUDF_USE_BENCHMARK_STATIC option to build and statically link Benchmark.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[robertmaynard]

I tempted to say that we should always use static nvbench and gbench to remove any need for these libraries in our test env.

@bdice your thoughts?

[bdice]

I was just about to say the same thing. I was hunting for a previous discussion of this topic and couldn't find it. We've discussed always statically linking nvbench/gbench and I think it would be a positive change.

[robertmaynard]

I was just about to say the same thing. I was hunting for a previous discussion of this topic and couldn't find it. We've discussed always statically linking nvbench/gbench and I think it would be a positive change.

It might have been on raft, as they are now only using static for benchmark libraries.

[bdice]

Here's the most recent conversation where this was discussed: rapidsai/raft#1874 (review)

[vyasr]

I'd be in favor of statically linking gbench/nvbench. Could we also do the same for tests?

[vyasr]

This was addressed in #15534. We now use static gtest, benchmark, and nvbench everywhere.