Skip to content
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 deprecation warning with cmake <3.5 #86

Open
theodoregoetz opened this issue Feb 26, 2024 · 0 comments · May be fixed by #87
Open

CMake deprecation warning with cmake <3.5 #86

theodoregoetz opened this issue Feb 26, 2024 · 0 comments · May be fixed by #87

Comments

@theodoregoetz
Copy link

Configuring with CMake causes build-system warnings

When configuring with cmake version 3.27 (and perhaps earlier versions as well), this warning is issued:

CMake Deprecation Error at external/argh/CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

To Reproduce

Configure argh using cmake

cmake -B build -S .

Expected behavior

No warnings on cmake configure.

Environment

Tested on Fedora Linux, but this probably manifests on all operating systems.

Additional context

  • CMake 3.1.0 was released on Dec 17, 2014
  • CMake 3.5.0 was released on Mar 8, 2016
  • Latest release is 3.28.3 which was Feb 5, 2024
theodoregoetz added a commit to theodoregoetz/argh that referenced this issue Feb 26, 2024
CMake 3.27 issued a deprecation warning saying cmake <3.5 would no longer
be supported.

closes adishavit#86
theodoregoetz added a commit to theodoregoetz/argh that referenced this issue Feb 27, 2024
CMake 3.27 issued a deprecation warning saying cmake <3.5 would no longer
be supported.

closes adishavit#86
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant