Allow rapids_test to be used without CUDAToolkit

[robertmaynard]

Description

Fixes #478

Checklist

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

[Jacobfaib]

A few minor issues. Also another more minor nit, the configure steps here are quite chatty:

-- Could not find nvcc, please set CUDAToolkit_ROOT.
'/opt/homebrew/opt/ccache/libexec/c++' '/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp' '-o' '/path/to/rapids-cmake/generate_ctest_json'

Is it possible to silence these unless there is a problem (or extra verbosity is requested)? The first message implies there is a problem (which there isn't), while the second is not useful for the user to see unless there is an issue.

[robertmaynard]

A few minor issues. Also another more minor nit, the configure steps here are quite chatty:

-- Could not find nvcc, please set CUDAToolkit_ROOT.
'/opt/homebrew/opt/ccache/libexec/c++' '/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp' '-o' '/path/to/rapids-cmake/generate_ctest_json'

Is it possible to silence these unless there is a problem (or extra verbosity is requested)? The first message implies there is a problem (which there isn't), while the second is not useful for the user to see unless there is an issue.

Can you try the updated version again, please? All your issues should be resolved now

[Jacobfaib]

Can you try the updated version again, please? All your issues should be resolved now

OK tried latest 07e58cd, and it seems that the build is still outputting the following:

'/opt/homebrew/opt/ccache/libexec/c++' '/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp' '-o' '/path/to/rapids-cmake/generate_ctest_json'

From what I can tell this is due to the compile command having the COMMAND_ECHO STDOUT option set. Perhaps this can be directed into a variable instead?

Also, I'm sure CI will flag this momentarily, but...

/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp:43:76: error: no member named 'minor' in 'version'
  buffer << "\"version\": {\"major\": " << v.major << ", \"minor\": " << v.minor << "}";
                                                                         ~ ^

[robertmaynard]

Can you try the updated version again, please? All your issues should be resolved now

OK tried latest 07e58cd, and it seems that the build is still outputting the following:

'/opt/homebrew/opt/ccache/libexec/c++' '/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp' '-o' '/path/to/rapids-cmake/generate_ctest_json'

From what I can tell this is due to the compile command having the COMMAND_ECHO STDOUT option set. Perhaps this can be directed into a variable instead?

Also, I'm sure CI will flag this momentarily, but...

/path/to/_deps/rapids-cmake-src/rapids-cmake/test/detail/generate_resource_spec.cpp:43:76: error: no member named 'minor' in 'version'
  buffer << "\"version\": {\"major\": " << v.major << ", \"minor\": " << v.minor << "}";
                                                                         ~ ^

Yeah I missed the COMMAND_ECHO, thanks. Removed that and only dump the compile info when we fail.

[Jacobfaib]

OK, with a quick fixup to fix that compile error above, the latest LGTM.

[robertmaynard]

/merge