Notes |
|
|
And no offense to Pol M, the previous qt4_wrap_ui() that commit mentioned in OP was likely predating CMake 3.0 too. |
|
|
(0021463)
|
Pol M
|
2020-06-15 00:22
|
|
Pretty in favor, I did not know this existed and it seems cleaner and more future proof. Any shenanigans that we do in cmake that can be automated further are a clear improvement.
No offense taken, I just took the simple path as at the time that was as much as it was needed. |
|
|
(0021708)
|
Blzut3
|
2021-08-10 07:57
|
|
|
|
|
Quote
-cmake_minimum_required(VERSION 2.8.12)
+cmake_minimum_required(VERSION 3.5...3.21)
Quote from cmake_minimum_required — CMake 3.21.1 Documentation If the running version of CMake is older than 3.12, the extra ... dots will be seen as version component separators, resulting in the ...<max> part being ignored and preserving the pre-3.12 behavior of basing policies on <min>.
'https://cmake.org/cmake/help/v3.21/command/cmake_minimum_required.html [^]'
Should that be cmake_minimum_required(VERSION 3.5) instead?
Quote
-if (POLICY CMP0071)
- cmake_policy(SET CMP0071 NEW)
-endif()
Quote from CMP0071 — CMake 3.21.1 Documentation New in version 3.10.
Quote from CMP0071 — CMake 3.21.1 Documentation CMake version 3.21.1 warns when the policy is not set and uses OLD behavior.
'https://cmake.org/cmake/help/v3.21/policy/CMP0071.html [^]' |
|
|
|
Sorry, I had misunderstood or misread the cmake_minimum_required documentation. |
|
|
(0021712)
|
Blzut3
|
2021-08-10 09:23
|
|
Yeah the point of using a range is so that you can keep the minimum low while having all the new policies set to NEW automatically. I suppose you're correct that 3.10 and 3.11 would raise a warning on that though. |
|
|
|
What requires CMake 3.5? As far as I know, AUTOUIC was introduced in 3.0. |
|
|
|
Maybe the attached patches 0001 & 0002 address the notes from the previous code review. But I didn't compile this.
|
|
|
|
Also fyi, using AUTOUIC means we no longer support Ubuntu 14.04 LTS (which I believe only has extended security maintenance until April 2022, and has ended standard support already), which ships with CMake 2.8.12. Ubuntu 16.04 LTS is not affected - it has CMake 3.5. |
|
|
(0021716)
|
Blzut3
|
2021-08-10 10:26
|
|
Can't comment on the patches right now, but as far as the 3.5 requirement that comes from practicality. This change requires 3.0, going to 3.1 allows dropping some legacy junk. It's not impossible that 3.1 could be the new literal minimum, but why spend cycles figuring that out? We only test for 3.5+ since that's what our CI container has. Given that we only really support Ubuntu 18.04+ and similar era distributions at this point (per policy of following Canonical's free support period) we really could bump it to 3.10, so 3.5 is being plenty generous I think. |
|
|
(0021720)
|
Blzut3
|
2021-08-10 17:55
|
|
Patch 0001 - I believe we can just use cmake_policy(VERSION 3.21) with a comment that it can be removed after the minimum becomes 3.12. Would need to test.
Patch 0002 - The line can just be removed. I thought I did remove it, but I guess not.
Patch 0003 - That policy was introduced in 3.0 so even if the minimum was set to that this policy should always be NEW anyway.
|
|
|
(0021725)
|
Blzut3
|
2021-08-15 02:44
|
|
|
|
(0022155)
|
Blzut3
|
2022-03-23 02:27
|
|
Going to consider this one resolved since we managed a release and it doesn't seem any issues came from it. |
|