This is useful for performing an operationīefore or after building the target. The second signature adds a custom command to a target such as a Target-level dependency on generate_table_csv, so the targets using them,įoo and bar, will not build until after target generate_table_csv The custom commands generating foo.cxx and bar.cxx each specify a Since foo and bar are independent targets that mayīuild concurrently, we prevent them from racing to generate table.csvīy placing its custom command in a separate target, generate_table_csv. Is needed only by target bar, but both targets need table.csv, Output foo.cxx is needed only by target foo and output bar.cxx Source tree is mentioned as an absolute source file path elsewhereĪdd_custom_command( OUTPUT table.csv COMMAND makeTable - i $ /input.dat VERBATIM ) add_custom_target( generate_table_csv DEPENDS table.csv ) add_custom_command( OUTPUT foo.cxx COMMAND genFromTable - i table.csv - case foo - o foo.cxx DEPENDS table.csv # file-level dependency generate_table_csv # target-level dependency VERBATIM ) add_library( foo foo.cxx ) add_custom_command( OUTPUT bar.cxx COMMAND genFromTable - i table.csv - case bar - o bar.cxx DEPENDS table.csv # file-level dependency generate_table_csv # target-level dependency VERBATIM ) add_library( bar bar.cxx ) The path in the build directory is preferred unless the path in the The current source directory ( CMAKE_CURRENT_SOURCE_DIR). The build directory corresponding to the current source directory If an output file name is a relative path, its absolute path isĭetermined by interpreting it relative to: If the output of the custom command is not actually createdĪs a file on disk it should be marked with the SYMBOLIC
Specify the output files the command is expected to produce.Įach output file will be marked with the GENERATED Gets silently overwritten by a custom command specification. Library or an executable) counts as an implicit main dependency which Each source file may have at most one command Treated just like any value given to the DEPENDS optionīut also suggests to Visual Studio generators where to hang Specify the primary input source file to the command. Using a pool that is not defined by JOB_POOLS causesĪn error by ninja at build time. Incompatible with USES_TERMINAL, which implies If any dependency is an OUTPUT of another custom command in the sameĭirectory ( CMakeLists.txt file), CMake automatically brings the otherĬustom command into the target in which this command is built. Otherwise, a file-level dependency is created on that path relative Source directory, a file-level dependency is created on that If the argument is a relative path and it exists in the current If the argument is the name of a source file that has beenĪdded to a target or on which a source file property has been set,Ī file-level dependency is created on that source file. If the argument is an absolute path, a file-level dependency Additionally, if the target is anĮxecutable or library, a file-level dependency is created toĬause the custom command to re-run whenever the target is If the argument is the name of a target (created by theĪdd_custom_target(), add_executable(), orĪdd_library() command) a target-level dependency isĬreated to make sure the target is built before any target Specify files on which the command depends. New in version 3.26: Arguments to COMMENT may use Options are currently ignored when APPEND is given, but may be The COMMENT, MAIN_DEPENDENCY, and WORKING_DIRECTORY The appended commands and dependencies apply to all configurations.
#Cmake print generator#
The output specified by the current call must match in at least oneĬonfiguration after evaluating generator expressions. If the previous call specified the output via a generator expression, There must have alreadyīeen a previous call to this command with the same output. See theĮxample: Generating Files for Multiple Targets below.Īppend the COMMAND and DEPENDS option values to the customĬommand for the first output specified. Instead, use the add_custom_target() command to drive theĬommand and make the other targets depend on that one. May build in parallel or the instances of the rule may conflict. Is given a rule to generate the file using the command at build time.ĭo not list the output in more than one independent target that That specifies any output of the custom command as a source file This defines a command to generate specified OUTPUT file(s).Ī target created in the same directory ( CMakeLists.txt file) Add_custom_command( OUTPUT output1 COMMAND command1.
0 kommentar(er)
