... | @@ -457,7 +457,7 @@ property set to true.) |
... | @@ -457,7 +457,7 @@ property set to true.) |
|
|
|
|
|
You can also use ADD_CUSTOM_COMMAND when the [generator command is
|
|
You can also use ADD_CUSTOM_COMMAND when the [generator command is
|
|
another executable in the same
|
|
another executable in the same
|
|
project](FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F "wikilink").
|
|
project](FAQ#how-do-i-generate-an-executable-then-use-the-executable-to-generate-a-file "wikilink").
|
|
|
|
|
|
Sometimes, the program doing the generation may generate multiple output
|
|
Sometimes, the program doing the generation may generate multiple output
|
|
files that each need to be part of the build. CMake 2.4 or higher
|
|
files that each need to be part of the build. CMake 2.4 or higher
|
... | @@ -511,7 +511,7 @@ property.) |
... | @@ -511,7 +511,7 @@ property.) |
|
### How can I add a dependency to a source file which is generated in a subdirectory?
|
|
### How can I add a dependency to a source file which is generated in a subdirectory?
|
|
|
|
|
|
Rules created with `ADD_CUSTOM_COMMAND` as
|
|
Rules created with `ADD_CUSTOM_COMMAND` as
|
|
[above](FAQ#How_can_I_generate_a_source_file_during_the_build.3F "wikilink")
|
|
[above](FAQ#how-can-i-generate-a-source-file-during-the-build "wikilink")
|
|
have scope only in the directory in which they are specified. If the
|
|
have scope only in the directory in which they are specified. If the
|
|
generated file is needed in another directory, a target-level dependency
|
|
generated file is needed in another directory, a target-level dependency
|
|
needs to be added. Create a target in the subdirectory with the custom
|
|
needs to be added. Create a target in the subdirectory with the custom
|
... | @@ -1377,8 +1377,8 @@ target. |
... | @@ -1377,8 +1377,8 @@ target. |
|
### What is the best way to distribute source code or binaries for a cmake-based project?
|
|
### What is the best way to distribute source code or binaries for a cmake-based project?
|
|
|
|
|
|
For creating source or binary packages there is now
|
|
For creating source or binary packages there is now
|
|
[CPack](Home#CPack "wikilink") coming with CMake, see the
|
|
[CPack](Home#cpack "wikilink") coming with CMake, see the
|
|
[documentation](Home#CPack "wikilink").
|
|
[documentation](Home#cpack "wikilink").
|
|
|
|
|
|
Of course you can also use any other ways to create packages.
|
|
Of course you can also use any other ways to create packages.
|
|
|
|
|
... | @@ -1939,7 +1939,7 @@ target depending on both targets and then make that. |
... | @@ -1939,7 +1939,7 @@ target depending on both targets and then make that. |
|
|
|
|
|
See the multi-level makefile layout described in the answer to the
|
|
See the multi-level makefile layout described in the answer to the
|
|
[above
|
|
[above
|
|
question](#Why_does_CMake_generate_recursive_Makefiles.3F "wikilink").
|
|
question](#why-does-cmake-generate-recursive-makefiles "wikilink").
|
|
It's the first level's invocation of the second level that needs to be
|
|
It's the first level's invocation of the second level that needs to be
|
|
re-worked and perhaps combined in order to fix this limitation. However,
|
|
re-worked and perhaps combined in order to fix this limitation. However,
|
|
the first level is what allows one to run "make" from any subdirectory
|
|
the first level is what allows one to run "make" from any subdirectory
|
... | | ... | |