diff options
| author | Brad King <brad.king@kitware.com> | 2021-05-14 15:46:48 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2021-05-17 14:01:57 (GMT) |
| commit | d8d0f3ec377380af07b3185e82a4d853f556e4f9 (patch) | |
| tree | 1160cb7a2617b6a5a6ead745db9ce575888b80c4 /Tests/RunCMake/WriteBasicConfigVersionFile | |
| parent | f3b46057414a9face8724a431fc6473b444d68c5 (diff) | |
| download | CMake-d8d0f3ec377380af07b3185e82a4d853f556e4f9.zip CMake-d8d0f3ec377380af07b3185e82a4d853f556e4f9.tar.gz CMake-d8d0f3ec377380af07b3185e82a4d853f556e4f9.tar.bz2 | |
Makefiles: Remove non-functioning relative path conversion
In CMake 3.6 and below, running
cmake --build . --target "$(pwd)/SomeTarget"
with a Makefiles generator automatically converted the target
name and invoked `make SomeTarget`. This made the build command
work even though
make "$(pwd)/SomeTarget"
would fail. This behavior was not implemented for any other generators,
and does not make sense because `cmake --build` is supposed to be a thin
wrapper around the native build tool. It has also been broken since
commit 8d47a20f13 (cmOutputConverter: use new ConvertToRelativePath
signature internally, 2016-06-16, v3.7.0-rc1~90^2~1) because cmState's
relative path conversion logic is not initialized in `cmake --build`.
Remove the non-functioning code.
Diffstat (limited to 'Tests/RunCMake/WriteBasicConfigVersionFile')
0 files changed, 0 insertions, 0 deletions
