Update minimal CMake version in favour of advances features it offers#8336
Conversation
|
Starting build on |
|
Build failed on ROOT-performance-centos8-multicore/default. Errors:
|
|
Build failed on ROOT-debian10-i386/cxx14. Errors:
|
0b31f44 to
f4bd71b
Compare
|
Starting build on |
|
Build failed on ROOT-performance-centos8-multicore/default. |
| cmake_minimum_required(VERSION 3.16 FATAL_ERROR) | ||
| else() | ||
| cmake_minimum_required(VERSION 3.9 FATAL_ERROR) | ||
| cmake_minimum_required(VERSION 3.12 FATAL_ERROR) |
There was a problem hiding this comment.
Wasn't this supposed to be 3.16? Also, I supposed in the same PR one should search and remove hacks for older versions (like the Python setup), as that will not be necessary anymore.
There was a problem hiding this comment.
@amadio sadly we can't move directly to 3.16 because Debian 10 has only cmake 3.13 packaged https://pkgs.org/search/?q=cmake
There was a problem hiding this comment.
Ok, if you want to keep Debian 10 support, I guess 3.12 is the minimal version to be worth an update.
There was a problem hiding this comment.
I updated to 3.13 which is a bit closer to 3.16
There was a problem hiding this comment.
I'd find it reasonable to install CMake 3.16 on our Debian machines, and to expect packagers to have to do the same. After all it's not a runtime requirement.
Can people still build against ROOT with older CMake?
There was a problem hiding this comment.
I believe yes, but we will need to remove hacks #8280 or even maybe more workarounds somewhere..
There was a problem hiding this comment.
(I will test such combination with rootest.git)
f4bd71b to
3c86e9f
Compare
|
Starting build on |
|
Build failed on ROOT-performance-centos8-multicore/default. |
|
@amadio looks like it will be still impossible to remove Python hacks in https://github.com/root-project/root/blob/master/cmake/modules/SearchRootCoreDeps.cmake: |
|
Yes, I was thinking about the move happening to 3.16. If it's only to 3.12 or 3.13, then the hacks need to stay. However, it's probably better to drop Debian 10 support and go to CMake 3.16. Debian 10 users can still have up to ROOT 6.24 if they don't want to install CMake by hand. |
|
About debian looks like users can get higher cmake version from |
3c86e9f to
c74183c
Compare
|
Starting build on |
|
Build failed on ROOT-performance-centos8-multicore/default. |
|
Build failed on ROOT-debian10-i386/cxx14. Errors:
|
|
Build failed on mac1014/python3. Errors:
|
|
Build failed on ROOT-ubuntu16/nortcxxmod. Failing tests: |
|
Build failed on mac11.0/cxx17. Errors:
|
|
@phsft-bot build! |
|
Starting build on |
|
Build failed on ROOT-debian10-i386/cxx14. Errors:
|
|
Build failed on ROOT-performance-centos8-multicore/default. Errors:
|
|
@oshadura then why was it not failing before? |
|
@bellenot Maybe my guess is wrong, checking other PR https://lcgapp-services.cern.ch/root-jenkins/job/root-pullrequests-build/121249/consoleFull I see that python3.8 is actually available on this node. Do you know if CMake was updated on this node as well? |
|
@phsft-bot build just on mac11.0/cxx17 |
|
Starting build on |
No idea. @Axel-Naumann ? |
|
Build failed on mac11.0/cxx17. Errors:
|
|
Yes cmake is updated, I will check where is a problem: |
…lable in this version
85c7499 to
186a2f0
Compare
|
Starting build on |
|
Build failed on mac1014/python3. Errors:
|
|
@bellenot I think now PR is ready, before I made a small typo. The only problem is that all MacOS nodes need to have updated CMake (e.g. see macphsft17.dyndns.cern.ch)... |
|
Thanks a lot @oshadura ! I'll ask @Axel-Naumann if one can update CMake on all the MacOS nodes |
|
Build failed on ROOT-debian10-i386/cxx14. Failing tests: |
|
@phsft-bot build |
|
Starting build on |
|
@phsft-bot build |
|
Starting build on |
|
Build failed on ROOT-debian10-i386/cxx14. Errors:
Failing tests: |
…root-project#8336) * Update minimal CMake version in favour of advances features it offers * Remove workaround for FindDoxygen (cmake < 3.13) * Remnove workaround for cmake < 3.14 to able to report issue directly to stdout * Remove workaround for CMake < 3.14 when Ninja 1.9.0 builds static libraries twice * Remove other CMake hack from multi-python ROOT builds * We are using 3.16 as a min CMake version and REGEX is definitely available in this version * Remove code used to search Python2/Python3 with <= CMake 3.14
Fixes as well #8280
(Thanks a lot to @amadio for pointing out the most reasonable for ROOT build system)
Update: sadly we can't move directly to 3.16 because Debian 10 has only cmake 3.13 packaged https://pkgs.org/search/?q=cmake