I worry that this will not be sufficient for downstream consumers -- eg. a project using nvbench might fail to find these at runtime without the user reconfig'ing their path manually.
Here's how we handled this "back in the day" before we yanked msvc the first time. It copied the dependent dlls into same dir as nvbench's binaries, so that transitive linking should work without extra setup (IIRC).
https://github.com/NVIDIA/nvbench/blob/pre_msvc_drop/cmake/NVBenchDependentDlls.cmake
Originally posted by @alliepiper in #354 (comment)
I worry that this will not be sufficient for downstream consumers -- eg. a project using nvbench might fail to find these at runtime without the user reconfig'ing their path manually.
Here's how we handled this "back in the day" before we yanked msvc the first time. It copied the dependent dlls into same dir as nvbench's binaries, so that transitive linking should work without extra setup (IIRC).
https://github.com/NVIDIA/nvbench/blob/pre_msvc_drop/cmake/NVBenchDependentDlls.cmake
Originally posted by @alliepiper in #354 (comment)