Every couple of years, it's generally good to increment CMake's minimum version used to build PROJ. It was 2 years ago for PROJ 9.4 that the minimum CMake was changed from 3.9 to 3.16 (#3997).
This issue is a general discussion to see if we can agree if PROJ's minimum CMake version should be increased for the PROJ 9.9.x series (anticipated September 2026), and what version it should go to. Note that RFC 3 says that "software packages will always be at least two years old", so the upper limit could be CMake 3.29-ish (released March 21, 2024).
Refer to What’s new in CMake for a handy/quick view of features from CMake releases.
For example, I see a decent case in #4753 that the minimum should be moved to 3.18 (or even 3.22). Are there other case examples that would benefit from other modern versions of CMake?
Every couple of years, it's generally good to increment CMake's minimum version used to build PROJ. It was 2 years ago for PROJ 9.4 that the minimum CMake was changed from 3.9 to 3.16 (#3997).
This issue is a general discussion to see if we can agree if PROJ's minimum CMake version should be increased for the PROJ 9.9.x series (anticipated September 2026), and what version it should go to. Note that RFC 3 says that "software packages will always be at least two years old", so the upper limit could be CMake 3.29-ish (released March 21, 2024).
Refer to What’s new in CMake for a handy/quick view of features from CMake releases.
For example, I see a decent case in #4753 that the minimum should be moved to 3.18 (or even 3.22). Are there other case examples that would benefit from other modern versions of CMake?