You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks. This is already resolved on develop, which I've just verified configures cleanly with a current CMake nightly (the 4.5 track): CUDA via CUDAToolkit (CMP0146 NEW), Boost via its CMake config (CMP0167 NEW), cmake_minimum_required(VERSION 3.24), and no policy or deprecation warnings.
The released 2.4.0 was the one at risk: it used cmake_minimum_required(VERSION 3.18) and CMP0146 OLD, and under CMake 4.x the OLD FindCUDA behavior is on its way to a hard error. develop modernized both, so the next release will configure out of the box.
On the -DCMAKE_POLICY_VERSION_MINIMUM=3.5 you added in the port: OpenMVS's own CMake files are all at 3.24, so that flag is being needed by one of the dependencies' installed CMake configs rather than by OpenMVS itself. Nothing to change upstream here — just confirming the OpenMVS side is clean on develop.
Closing: this is resolved on develop, which I verified configures cleanly with a current CMake nightly (the 4.5 track) — CUDA via CUDAToolkit (CMP0146 NEW), Boost via its CMake config (CMP0167 NEW), cmake_minimum_required(VERSION 3.24), no policy or deprecation warnings. The fix will ship with the next release.
If a configure still fails for you against develop (as opposed to the released 2.4.0, which had CMP0146 OLD / min 3.18), please reopen with the CMake error log and I'll take another look.
Activity
cdcseacave commentedon Oct 13, 2026
Thanks. This is already resolved on
develop, which I've just verified configures cleanly with a current CMake nightly (the 4.5 track): CUDA viaCUDAToolkit(CMP0146NEW), Boost via its CMake config (CMP0167NEW),cmake_minimum_required(VERSION 3.24), and no policy or deprecation warnings.The released 2.4.0 was the one at risk: it used
cmake_minimum_required(VERSION 3.18)andCMP0146 OLD, and under CMake 4.x the OLDFindCUDAbehavior is on its way to a hard error.developmodernized both, so the next release will configure out of the box.On the
-DCMAKE_POLICY_VERSION_MINIMUM=3.5you added in the port: OpenMVS's own CMake files are all at3.24, so that flag is being needed by one of the dependencies' installed CMake configs rather than by OpenMVS itself. Nothing to change upstream here — just confirming the OpenMVS side is clean ondevelop.cdcseacave commentedon Oct 13, 2026
Closing: this is resolved on
develop, which I verified configures cleanly with a current CMake nightly (the 4.5 track) — CUDA viaCUDAToolkit(CMP0146NEW), Boost via its CMake config (CMP0167NEW),cmake_minimum_required(VERSION 3.24), no policy or deprecation warnings. The fix will ship with the next release.If a configure still fails for you against
develop(as opposed to the released 2.4.0, which hadCMP0146 OLD/ min 3.18), please reopen with the CMake error log and I'll take another look.