Skip to content

Revisit handling dependent DLLs on Windows #369

@oleksandr-pavlyk

Description

@oleksandr-pavlyk

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions