installing a pre-built module and its various dependencies

[ben.boeckel (Ben Boeckel (Kitware))]

@wuziq

target_link_libraries doesn’t work because then Foo.dll is on the link line, which produces a link error.

Right, the module is only loadable, so the linker doesn’t care about it.

@wuziq

As a result, Foo’s include directory also isn’t added to the application’s header search paths, and target_include_directories(App PUBLIC Foo) doesn’t seem to work, either.

I would make a second INTERFACE target with the compilation requirements. You can then add this to Foo::Foo’s interface (for whatever it’s worth) and use it in any consuming bit. Calling it Foo::Headers or Foo::SDK is probably apt.

@wuziq

The best way to install all of Foo.dll’s dependencies along with the application.

file(GET_RUNTIME_DEPENDENCIES) should work here.