New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cmake version tracking issue #24004
Comments
And to complement this excellent write-up, a summary of which distro version comes with which CMake version: Debian
Ubuntu
Fedora
The biggest blocker is that we use an 18.04 image in our release workflow to support GLIBC 2.27. We'd either have to build a new CMake on that runner ourselves, or finally drop support for GLIBC 2.27 (20.04 has 2.29). |
This comment was marked as resolved.
This comment was marked as resolved.
https://repology.org/project/cmake/versions gotchu covered |
I don't think we need to track backport/non-standard versions. I interpreted this issue to be about mainline/release distro versions only without any additional modifications. It is e.g. trivial to simply build latest cmake on any system. |
Yup, just added that for the sake of completeness (and to prevent "but did you know you could install later versions manually?" comments). |
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to transition from using ExternalProject to FetchContent, which is more flexible and requires less hacks than ExternalProject to work properly. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. This also removes broken `--version` generation as it does not work for version 3.10 and 3.11 due to the `JOIN` generator expression. Reference: neovim#24004
The benefits are primarily being able to use FetchContent, which allows for a more flexible dependency handling. Other various quality-of-life features such as `-B` and `-S` flags are also included. This also removes broken `--version` generation as it does not work for version 3.10 and 3.11 due to the `JOIN` generator expression. Reference: #24004
A tracking issue of pros and cons of upgrading the minimum cmake version (currently 3.13).
Note: "Drops support" sounds worse than it actually is; it only means that
neovim can't be built with the cmake that is provided by the package manager by
default. It's still very easy to build and download any cmake version (either
manually or with something like PPA/backports).
3.14
FetchContent_MakeAvailable
Drops support for
3.15
--install
flag$<REMOVE_DUPLICATES>
generator expression--version
logic.-G
isn't providedDrops support for
3.16
3.17
Drops support for
3.18
REQUIRED
option for all "find_" commands.Drops support for
3.19
string
gainedJSON
subcommandscmake.deps/deps.txt
Drops support for
The text was updated successfully, but these errors were encountered: