thx, that's a relief. Let's hope a release pops up soon, because basically to me 2.15.0 is of no use. Mistakes happen, so looking forward to the maintenance release.
I used to have the following (little snippet) during the install phase: -- Installing: /opt/cppcheck/bin/cppcheck -- Installing: /opt/cppcheck/share/Cppcheck/addons/init.py -- Installing: /opt/cppcheck/share/Cppcheck/addons/cppcheck.py -- Installing: /opt/cppcheck/share/Cppcheck/addons/cppcheckdata.py -- Installing: /opt/cppcheck/share/Cppcheck/addons/findcasts.py -- Installing: /opt/cppcheck/share/Cppcheck/addons/misc.py -- Installing: /opt/cppcheck/share/Cppcheck/addons/misra.py -- Installing:...
* compiler : support for the c++ standards 23 and 26 (and their gnu extensions
Can a new release be made, since we are building this in an automated way, and would want to avoid that I need to adjust the build script to 'sed' a solution ;-) (for the version issue) This was my analysis, just for reference, since problem is solved in the meantime. The problem is cmake/versions.cmake SET(VERSION "2.11") STRING(REGEX MATCHALL "[0-9]+" VERSION_PARTS "${VERSION}") LIST(GET VERSION_PARTS 0 VERSION_MAJOR) LIST(GET VERSION_PARTS 1 VERSION_MINOR) LIST(GET VERSION_PARTS 2 VERSION_PATCH)...
also with cmake 3.26.4. The problem is cmake/versions.cmake SET(VERSION "2.11") STRING(REGEX MATCHALL "[0-9]+" VERSION_PARTS "${VERSION}") LIST(GET VERSION_PARTS 0 VERSION_MAJOR) LIST(GET VERSION_PARTS 1 VERSION_MINOR) LIST(GET VERSION_PARTS 2 VERSION_PATCH) <========== there is no 3rd field So as suggested above changing to "2.11.0" fixes the problem. Cmake error : CMake Error at cmake/versions.cmake:6 (LIST): LIST index: 2 out of range (-2, 1) Call Stack (most recent call first): CMakeLists.txt:13...
as described in the other ticket, I think -Wextra should return, this is sticking our head in the ground and lowering the quality checks on the code base
but that is the thing we do not want to do, -Wextra is there to increase the warning level and catch mistakes, disabling it all is like sticking our head in the ground and throw away all the benefits. the -isystem will just shut up those warnings on headers from that include path
-isystem : why would that not be acceptable ?