In a number of places in our build, we use compiled binaries via
add_custom_command and friends to perform work during the compilation. For
the most part we are able to successfully specify the target name used with
add_executable in place of a full path to successfully tell CMake to run
the
If you want add_custom_command to run a certain executable, simply
give it the full path to that executable: use /full/path/to/tool
instead of tool
If tool is a built thing, you can use
${XYZ_BINARY_DIR}/${CMAKE_CFG_INTDIR}/tool which will properly
expand out to the correct Release or Debug
On 06.03.12 17:56:41, David Cole wrote:
If you want add_custom_command to run a certain executable, simply
give it the full path to that executable: use /full/path/to/tool
instead of tool
If tool is a built thing, you can use
${XYZ_BINARY_DIR}/${CMAKE_CFG_INTDIR}/tool which will properly
On Tue, Mar 6, 2012 at 6:27 PM, Andreas Pakulat ap...@gmx.de wrote:
On 06.03.12 17:56:41, David Cole wrote:
If you want add_custom_command to run a certain executable, simply
give it the full path to that executable: use /full/path/to/tool
instead of tool
If tool is a built thing, you can
