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:33:55 (GMT) |
| commit | 3f976bf201983b399dacbcde51ef10b0a6de9b06 (patch) | |
| tree | 9cf6a87f19825fa2368f856e928e1e28ceedb5f3 /configure | |
| parent | e3185e3d1b92a95c18f22f70b3cef6944dd019eb (diff) | |
| download | CMake-3f976bf201983b399dacbcde51ef10b0a6de9b06.zip CMake-3f976bf201983b399dacbcde51ef10b0a6de9b06.tar.gz CMake-3f976bf201983b399dacbcde51ef10b0a6de9b06.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 'configure')
0 files changed, 0 insertions, 0 deletions