Hi there!
I've got a question I can't seem to find a good answer to: What is the
idiomatic way in CMake 3.0 to handle bundling shared libraries? I've
exhausted my google-fu and all of the examples seem to be from before
CMake 3 was released. None of them take any advantage of 3.0's new and
IMO much more elegant target usage requirements paradigm, and there
doesn't really seem to be consensus on what the best way to handle this
problem is.
Given some application <app> and some library <upstreamlib> with a
header, static, and shared library components (.h, .lib, and .dll on
windows), it seems like there should be some way to write a definition
for an interface library such that by writing target_link_library(<app>
<upstreamlib>), the appropriate shared libraries are copied to the exe
directory (or in some way made accessible) either via a special custom
target, a post build step, or install time. Static libraries and
headers are handled this way, so why not shared libraries too? Am I just
being naive?
Thanks for your help.
-Walter
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
