[CMake] List all binaries associated with a target.

[Roman Bolshakov]

2015-03-16 23:22 GMT+03:00 Klaim - Joël Lamotte <mjklaim at gmail.com>:

> Then you can invoke top-level cmake_install.cmake to install a subset
>> of your project:
>> DESTDIR=/destination/install/path cmake -DCOMPONENT=A -P
>> cmake_install.cmake
>>
>>
> It is not clear to me how all this would help installing automatically a
> library and it's dependencies
> when I modify then build the library.
> If my understanding is correct, all this need to be triggered by cmake
> install command, right?
> Also, the main issue is gathering binaries so that they can be debugged on
> windows (as you
> point later) without having to move files around, in particular
> dependencies binaries that
> can and will change through developement.
>
cmake install is not completely automatic (you need to define install
commands for dependencies and all targets explicitly) and is, indeed, a
separate step from build. If you're fine with explicit definition of
dependencies you might consider to tether build and install by an external
script. It would kick off build and if it succeeds it would proceed to the
cmake install-based pre-test packaging and start testing after then.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20150322/53ffeab8/attachment.html>