add_custom_command is rather used for operations performed during build phase
(which is completely separate off packaging)
You could create hgHash.txt during packaging by using install(SCRIPT) command:
install(SCRIPT hgHash.cmake)
install(
FILES hgHash.txt
DESTINATION yourapp
)
You might try to use CMAKE_CONFIGURE_DEPENDS
(http://www.cmake.org/cmake/help/v3.0/prop_dir/CMAKE_CONFIGURE_DEPENDS.html)
property:
set_property(DIRECTORY APPEND PROPERTY CMAKE_CONFIGURE_DEPENDS dependency.txt)
That would trigger CMake regeneration upon a change of dependency.txt
-Roma
Subject: Visual Studio add-in: adding non-cmake files as dependencies to
trigger re-generation
Hello
Is there a way to let the Visual Studio CMake add-in know that it needs to
regenerate the project when certain non-cmake files change?
I'm reading lists of file names from non-cmake txt files with
I am using CMake 2.8.12 on Windows. My directory/path name contains an
exclamation point (e.g. C:\!Code\CommandLineTooLong). I get a 'The command line
is too long.' error when linking an executable from 100 objects.
After poking around in cmGlobalNinjaGenerator.cxx, this is what I think is
caus
Thanks for clarification, JC. The links you provided are a good read.
However, I would like to avoid "super-build" technique. It needlessly
(in my case) complicates and obfuscates things.
> In fact, all Find.cmake module are slowly been converted to create CMake
> imported targets.
Find
Hello,
I was trying to use the Graphviz feature on CMake and noticed a mistake on
the documentation where it says to use "--graphiz=foo" instead of
"--graphviz=foo" where the former doesn't work but the latter does.
I tried searching the different archives, but there is no mention about
this. Was
Hi Micha,
these parameters, which are common to several install() commands, are
described in the initial section of the command's docs:
http://www.cmake.org/cmake/help/v3.2/command/install.html#introduction
Petr
On Wed, Feb 18, 2015 at 8:46 AM, Micha Renner
wrote:
> Hello,
>
> In the manual th
