Re: [CMake] add_custom_command not triggered

On 31.10.2015 15:49, Nico Schlömer wrote: add_custom_command( OUTPUT ${CMAKE_BINARY_DIR}/test/data/pacman.e.2.0 COMMAND decomp -p 2 ${CMAKE_BINARY_DIR}/test/data/pacman.e DEPENDS noshTestFetchData ) I don't know anything about the ExternalData module but assuming this is unrelated ...

Re: [CMake] add_custom_command not triggered

Oh wait, I read it wrong... Try ${} to get the value of the variable. (It contains a file name, right?) D On Saturday, October 31, 2015, David Cole wrote: > Because you're giving DEPENDS as a target name, this is only an ordering > dependency, stating that the command

Re: [CMake] add_custom_command not triggered

Because you're giving DEPENDS as a target name, this is only an ordering dependency, stating that the command should run after the target is built. But not necessarily re-build whenever the target is re-built... If you want to re-run the command based on a file changing instead, then use the full