summaryrefslogtreecommitdiffstats
path: root/Modules/CMakeFindWMake.cmake
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2022-12-07 23:38:10 (GMT)
committerBrad King <brad.king@kitware.com>2022-12-07 23:39:37 (GMT)
commit5f2bf6ecc6b6fadca63da57188097a5f4f3d8854 (patch)
treef1af11b98aa5899ac0b8f44d5a6bf9ac8819bb90 /Modules/CMakeFindWMake.cmake
parent127fa54808acd80b658409758533c2522f6a1c19 (diff)
downloadCMake-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 'Modules/CMakeFindWMake.cmake')
0 files changed, 0 insertions, 0 deletions