That was one of the other problems I encountered during the initial conversion
to CMake. I fixed it by wrapping all the ADD_* commands with my own functions
which override the target’s output directory. Now we only need to install if a
script or static resource changes.
From: Klaim - Joël Lamot
On 18 August 2016 at 17:32, Klaim - Joël Lamotte wrote:
> The discussion led to a ticket for a potential feature: https://gitlab.
> kitware.com/cmake/cmake/issues/15450
> Discussion ended there: http://public.kitware.com/pipermail/cmake/2015-
> March/060120.html
>
http://cmake.3232098.n2.nabble.
On 18 August 2016 at 17:26, wrote:
> I’m working on an application which consists of many different components
> surrounding a common core. We ship multiple products from the same source
> tree by adding and/or removing components from the output application
> directory.
>
>
>
> Using CMake’s ins
I’m working on an application which consists of many different components
surrounding a common core. We ship multiple products from the same source tree
by adding and/or removing components from the output application directory.
Using CMake’s install system in this environment is proving difficu
