summaryrefslogtreecommitdiffstats
path: root/.editorconfig
diff options
context:
space:
mode:
authorBen Boeckel <ben.boeckel@kitware.com>2023-07-22 10:46:31 (GMT)
committerBen Boeckel <ben.boeckel@kitware.com>2023-07-22 11:12:43 (GMT)
commitb665966933c8656d1dafde06b8f29fe7e4901738 (patch)
tree3a006a29d8ced92cf5662cb7a9216c0f0cb8d8e7 /.editorconfig
parenta99b87a6285d9801ed429d5f44308b24c4706fb8 (diff)
downloadCMake-b665966933c8656d1dafde06b8f29fe7e4901738.zip
CMake-b665966933c8656d1dafde06b8f29fe7e4901738.tar.gz
CMake-b665966933c8656d1dafde06b8f29fe7e4901738.tar.bz2
cmComputeLinkInformation: track OBJECT library dependencies
In commit b6a5382217 (Ninja: depend on language module information files directly, 2023-02-10), introduced via !8197, language-specific module information files (`CMakeFiles/<target>.dir/<lang>Modules.json`) files were added as real dependencies to the dyndep collation steps. Previously, the behavior was to inform the collator of all possible targets and search for the files manually ignoring those which did not exist with ordering enforced by depending on the linker output of all dependent targets. This behavior could lead to stale information being used (e.g., if a target stops providing any targets) and also did not reliably build everything needed on rebuilds. Afterwards, the internal computation changed the dependency from all possible targets to an exact set of "these targets might have modules" query, however one that did not include `OBJECT` libraries since do not have `LinkEntry` items internally (their objects are instead treated as source files). As a stopgap measure, track `OBJECT` libraries in a separate list and query them explicitly when gathering targets which may have interesting information. Future work can add `LinkEntry` items to represent these targets once all `LinkEntry` consumers have been audited to make sure they are not surprised by any `OBJECT` library entries. Fixes: #25112
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions