[CMake] configuration based add_custom_command
Robert Bielik
robert.bielik at xponaut.se
Wed Aug 24 05:04:07 EDT 2011
Michael Wild skrev 2011-08-23 11:29:
> The easiest way around this I can see is to wrap the command in a
> CMake-script like this:
>
> add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/someFile.txt
> COMMAND ${CMAKE_COMMAND}
> -DCONFIG=$<CONFIGURATION>
> -DOUTPUT=${CMAKE_CURRENT_BINARY_DIR}/someFile.txt
> -P ${CMAKE_SOURCE_DIR}/generateSomeFile.cmake
> DEPENDS ${CMAKE_SOURCE_DIR}/generateSomeFile.cmake
> WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
> COMMENT "Generating someFile.txt"
> VERBATIM)
>
>
> And then, inside the generateSomeFile.cmake wrapper file you do:
>
> if(CONFIG STREQUAL Release)
> execute_process(COMMAND ...)
> endif()
>
>
> HTH
Ooh... I'll try it, but I don't understand it, yet :)
Feature request: A CONFIGURATION option to add_custom_command:
ADD_CUSTOM_COMMAND(
...
CONFIGURATION Release
...
)
would make life so much easier.
Regards,
/Rob
More information about the CMake
mailing list