diff options
| author | Brad King <brad.king@kitware.com> | 2023-03-02 18:46:44 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2023-03-02 19:28:26 (GMT) |
| commit | 771387523a02e0c1ef5f68d20e9efc210b19c868 (patch) | |
| tree | f6fe6fe687a42bd20bede30358d0cfeeca818375 /Modules/FortranCInterface.cmake | |
| parent | e2f1d6e7bdc398530fdd61b996ba1a87ecc54044 (diff) | |
| download | CMake-771387523a02e0c1ef5f68d20e9efc210b19c868.zip CMake-771387523a02e0c1ef5f68d20e9efc210b19c868.tar.gz CMake-771387523a02e0c1ef5f68d20e9efc210b19c868.tar.bz2 | |
ExternalProject: Restore driving install through build system
Revert commit 66b5d51f38 (ExternalProject: Install CMake projects
using 'cmake --install', 2022-09-08, v3.25.0-rc1~150^2).
It changed the ExternalProject install step command from:
cmake --build <dir> --target install --config <cfg>
to:
cmake --install <dir> --config <cfg>
The latter command no longer runs the external project build system
during the install step. We could consider using the commands:
cmake --build <dir> --target all --config <cfg>
cmake --install <dir> --config <cfg>
as the install step, but if `CMAKE_SKIP_INSTALL_ALL_DEPENDENCY` is
used in the external project, that can change semantics too.
Revert the original change pending further investigation on other ways
to support its motivating use case. Add a test covering the
previously-regressed use case.
Fixes: #24567
Issue: #23946
Diffstat (limited to 'Modules/FortranCInterface.cmake')
0 files changed, 0 insertions, 0 deletions