We may consider enabling this policy in the future, but for now just
suppress the warnings to preserve the backwards compatibility.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Makes sense to stick to the old behavior (which we know to work) for now. The new behavior seemed desirable for the future, though I haven't fully understood it yet.
Comment Actions
I'm using cmake version 3.20.3 and I don't think I've seen any warning so far. What happens on your side that prompted you to make this change?
Comment Actions
We see a lot of the following warning:
CMake Warning (dev) at /b/s/w/ir/x/w/cipd/share/cmake-3.19/Modules/ExternalProject.cmake:2240 (message): Policy CMP0114 is not set: ExternalProject step targets fully adopt their steps. Run "cmake --help-policy CMP0114" for policy details. Use the cmake_policy command to set the policy and suppress this warning. ExternalProject target 'stage2' would depend on the targets for step(s) 'really-install' under policy CMP0114, but this is being left out for compatibility since the policy is not set. Call Stack (most recent call first): /b/s/w/ir/x/w/llvm-project/clang/CMakeLists.txt:858 (ExternalProject_Add_StepTargets) This warning is for project developers. Use -Wno-dev to suppress it.
Here's an example: https://logs.chromium.org/logs/fuchsia/buildbucket/cr-buildbucket/8833340663294366177/+/u/clang/configure/stdout
Comment Actions
[Github PR transition cleanup]
I think this has been done now, I can see both being set in cmake/Modules/CMakePolicy.cmake.