diff options
| author | Brad King <brad.king@kitware.com> | 2022-12-07 23:38:10 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2022-12-07 23:39:37 (GMT) |
| commit | 5f2bf6ecc6b6fadca63da57188097a5f4f3d8854 (patch) | |
| tree | f1af11b98aa5899ac0b8f44d5a6bf9ac8819bb90 /Help/command | |
| parent | 127fa54808acd80b658409758533c2522f6a1c19 (diff) | |
| download | CMake-5f2bf6ecc6b6fadca63da57188097a5f4f3d8854.zip CMake-5f2bf6ecc6b6fadca63da57188097a5f4f3d8854.tar.gz CMake-5f2bf6ecc6b6fadca63da57188097a5f4f3d8854.tar.bz2 | |
Help: Drop misleading add_custom_command "makefile terms" explanation
The "In makefile terms" explanation is left from very early days of
CMake to help developers migrating from hand-written makefiles.
These days it is often misinterpreted, particularly in the context
of multiple `add_custom_command` calls, to mean that we generate a
single Makefile containing rules for all custom commands. This
leads to an incorrect mental model of the expressed build system.
The actual generated build system may spread the rules across multiple
targets that do not see the each other's file-level rules, which makes
target-level dependencies important too.
Diffstat (limited to 'Help/command')
| -rw-r--r-- | Help/command/add_custom_command.rst | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/Help/command/add_custom_command.rst b/Help/command/add_custom_command.rst index 5878997..4978075 100644 --- a/Help/command/add_custom_command.rst +++ b/Help/command/add_custom_command.rst @@ -35,10 +35,6 @@ Do not list the output in more than one independent target that may build in parallel or the two instances of the rule may conflict (instead use the :command:`add_custom_target` command to drive the command and make the other targets depend on that one). -In makefile terms this creates a new target in the following form:: - - OUTPUT: MAIN_DEPENDENCY DEPENDS - COMMAND The options are: |