diff options
| author | Brad King <brad.king@kitware.com> | 2020-03-30 15:08:10 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2020-03-30 15:24:27 (GMT) |
| commit | 5a95b5e091fa2a2d0ad869a80c37eaa980917853 (patch) | |
| tree | bc820a43004c4ea7ef90ee5c53ace0f587a72af2 /Tests/RunCMake/target_link_libraries/ConfigCase-result.txt | |
| parent | b7d8c91822101ff9de07075e9b1f02e18c2725da (diff) | |
| download | CMake-5a95b5e091fa2a2d0ad869a80c37eaa980917853.zip CMake-5a95b5e091fa2a2d0ad869a80c37eaa980917853.tar.gz CMake-5a95b5e091fa2a2d0ad869a80c37eaa980917853.tar.bz2 | |
target_link_libraries: Fix regression in case of $<CONFIG> genex
Since commit b8626261e9 (Precompile headers: Add methods to generate PCH
sources, 2019-07-13, v3.16.0-rc1~182^2~4) we look up source files for a
target using an upper-case configuration even though an original-case
name is sufficient. Since commit 36ded610af (PCH: Generate sources
during Compute step, 2019-10-05, v3.16.0-rc1~2^2) the source file lookup
is the first time we compute many on-demand structures that depend on
the configuration name. This caused the `$<CONFIG>` generator
expression to evaluate to the upper-case configuration name in some
cases where we used original-case before.
Fix this by switching the source file lookup to the original-case config
name. Add a test covering the symptom that led to the discovery of this
problem.
Fixes: #20517
Diffstat (limited to 'Tests/RunCMake/target_link_libraries/ConfigCase-result.txt')
| -rw-r--r-- | Tests/RunCMake/target_link_libraries/ConfigCase-result.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Tests/RunCMake/target_link_libraries/ConfigCase-result.txt b/Tests/RunCMake/target_link_libraries/ConfigCase-result.txt new file mode 100644 index 0000000..d00491f --- /dev/null +++ b/Tests/RunCMake/target_link_libraries/ConfigCase-result.txt @@ -0,0 +1 @@ +1 |