From 5f2bf6ecc6b6fadca63da57188097a5f4f3d8854 Mon Sep 17 00:00:00 2001 From: Brad King Date: Wed, 7 Dec 2022 18:38:10 -0500 Subject: 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. --- Help/command/add_custom_command.rst | 4 ---- 1 file changed, 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: -- cgit v0.12