hyperscan
hyperscan copied to clipboard
cmake deprecation warnings
$ cmake ../
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.10 will be removed from a future version of
CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
-- Build type RELWITHDEBINFO
-- using release build
CMake Warning (dev) at cmake/boost.cmake:17 (find_package):
Policy CMP0167 is not set: The FindBoost module is removed. Run "cmake
--help-policy CMP0167" for policy details. Use the cmake_policy command to
set the policy and suppress this warning.
Call Stack (most recent call first):
CMakeLists.txt:72 (include)
This warning is for project developers. Use -Wno-dev to suppress it.
-- Boost version: 1.83.0
CMake Warning (dev) at CMakeLists.txt:75 (find_package):
Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
are removed. Run "cmake --help-policy CMP0148" for policy details. Use
the cmake_policy command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.
Go to CMakeLists.txt in the source folder and where int he first line it is written cmake_minimum_required (VERSION 2.8.11) make it cmake_minimum_required (VERSION 1.10), and you are all set. 😀
That would worsen the issue.
That would worsen the issue.
Make it the version it shows after the < sign. For your case it's 3.10. So it must solve it. 😀
This issue is not about asking for workarounds. And no, I'm not gonna install ancient cmake.
This issue is not about asking for workarounds. And no, I'm not gonna install ancient cmake.
Bro wth you mean! The safest, fastest and easiest solution is, open CMakeLists.txt and where it is written cmake_minimum_required (VERSION 2.8.11) make it cmake_minimum_required (VERSION 3.10) and yes it solves it. I never said you to install any ancient CMAKE version, which I also don't support. That's the real quick and the only solution for now else you have to set some flags, which makes the process real complex. Read what I said first then comment. It isn't a error, it's a warning.