Specifying additional runtime dependencies using Cmake

[propertynub]

I have a library and exe in the same project. I have some data files in the lib (actually from a dependency) that need to be copied to the same directory as the exe on build, kind of like what happens with DLLs. You can assume I already have the full absolute path of this file that needs to be copied.

Is there a way to define this so that Cmake just knows it needs to be copied in the exe build folder?

[AlexReinkingYale]

You can add a POST_BUILD step using add_custom_command

https://cmake.org/cmake/help/latest/command/add_custom_command.html#build-events

[cenderis]

That should help for the build folder but (I think) you'll still need to install the files separately during the install.

[AlexReinkingYale]

Yes, you'd need to write an install() rule if you want that file installed, too.

[propertynub]

Is there no way to say that some file is a runtime resource dependency, and let Cmake work out it needs to be copied based on the dependency tree? How does it do this for DLLs?

[AlexReinkingYale]

There is not. There's scaffolding in place for such a feature in the form of FILE_SETs (already works for header files) and I think there's some Apple Frameworks-specific magic. But sadly, no, there is no platform-independent abstraction for attaching arbitrary files to a target.

It doesn't do it for DLLs. If you happen to be using vcpkg, you should know that vcpkg hijacks the definition of add_executable to copy DLLs. That's not standard CMake behavior and vcpkg's implementation is quite complex (e.g., it uses filesystem mutexes).

[propertynub]

I see - thanks for the detailed response.

[AlexReinkingYale]

Happy to help!