diff options
| author | Brad King <brad.king@kitware.com> | 2023-07-05 15:40:37 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2023-07-06 12:11:34 (GMT) |
| commit | 8a07bcc149d9c886cee924d9a68c8001b1011ae3 (patch) | |
| tree | 9fea8ec614829af78b69733feb7c228ae3a2096a /Help/guide/tutorial | |
| parent | b384058e4ba77defdff8741db636f60d6843d87d (diff) | |
| download | CMake-8a07bcc149d9c886cee924d9a68c8001b1011ae3.zip CMake-8a07bcc149d9c886cee924d9a68c8001b1011ae3.tar.gz CMake-8a07bcc149d9c886cee924d9a68c8001b1011ae3.tar.bz2 | |
MSVC: Restore support for non-incremental linking without 'rc' in PATH
Since commit 0b552eb877 (MSVC: Embed manifests directly for
non-incremental vs_link_exe links, 2023-02-20, v3.27.0-rc1~438^2) we
tell the MSVC `link` tool to embed manifests directly rather than
running `mt` ourselves. However, `link` expects `rc` to be in the PATH
when embedding manifests. Although that is normally true, some users
prepare minimal environments and explicitly specify include and link
directories for the Windows SDK. In such cases, `rc` is not in the PATH
and is explicitly specified in `CMAKE_RC_COMPILER`. Restore support for
such cases by explicitly adding the RC location to the end of the PATH.
Fixes: #25047
Diffstat (limited to 'Help/guide/tutorial')
0 files changed, 0 insertions, 0 deletions