As mentione in the README.md file of the repository [1], the previously published cppcheck snap was out-dated.
(Linux/Unix) The Canonical Snapcraft package is unmaintained and contains a very old version. Please refrain from using it! See https://trac.cppcheck.net/ticket/11641 for more details.
In the previous days, I got the ownership of the snap, created a new repository [2] , and published new releases for multiple architectures [3].
Would it be possible to update the corresponding sections from the website [4] and repository [5]?
But the "latest" is not "stable". The ".99" versions are the current dev versions and should be offered as such (if possible in Snap). "stable" versions should only be built from the version tags. The latest is 2.13.2.
I think the package should also contain the cppcheck-gui application.
This is a valid point. I can keep a distinction between the channels. It's clear to me how to proceed with the stable channel. Do you have any preference for candidate and beta? A straight-forward option here is to let them inherit the edge releases.
The Snap Store already contains a snap for cppcheck-gui[1]. It is undoubtedly outdated because the last release was in 2018. I think it would be better to not have two snaps for the same application. I can try sending an email to the current maintainer. Maybe he can start publishing new releases again or transfer ownership to me. An alternative (which is more confusing to the users) is building the cppcheck-gui application inside the new snap (cppcheck).
After fixing the aforementioned aspects and the Boost linking, I will create PRs for updating the documentation.
Hi,
As mentione in the
README.mdfile of the repository [1], the previously publishedcppchecksnap was out-dated.In the previous days, I got the ownership of the snap, created a new repository [2] , and published new releases for multiple architectures [3].
Would it be possible to update the corresponding sections from the website [4] and repository [5]?
[1] https://github.com/danmar/cppcheck
[2] https://github.com/iosifache/cppcheck-snap
[3] https://snapcraft.io/cppcheck
[4] https://cppcheck.sourceforge.io/#download
[5] https://github.com/danmar/cppcheck#packages
Many thanks,
Andrei
Thanks for reviving this.
But the "latest" is not "stable". The ".99" versions are the current dev versions and should be offered as such (if possible in Snap). "stable" versions should only be built from the version tags. The latest is 2.13.2.
I think the package should also contain the
cppcheck-guiapplication.The documentation changes can be done by yourself via pull requests:
https://github.com/danmar/cppcheck/pulls
https://github.com/danmar/cppcheck-htdocs/pulls
It would also make sense to remove the old
snapfolder in that PR.Also to get a more performant binary it should be built against Boost .
Hi Oliver,
This is a valid point. I can keep a distinction between the channels. It's clear to me how to proceed with the stable channel. Do you have any preference for candidate and beta? A straight-forward option here is to let them inherit the edge releases.
The Snap Store already contains a snap for
cppcheck-gui[1]. It is undoubtedly outdated because the last release was in 2018. I think it would be better to not have two snaps for the same application. I can try sending an email to the current maintainer. Maybe he can start publishing new releases again or transfer ownership to me. An alternative (which is more confusing to the users) is building thecppcheck-guiapplication inside the new snap (cppcheck).After fixing the aforementioned aspects and the Boost linking, I will create PRs for updating the documentation.
[1] https://snapcraft.io/cppcheckgui
Many thanks,
Andrei
You are also building a
Debugbuild. That should beRelWithDebInfo. If you use the latter there is also no need to manually enable the matchcompiler.For the sake of proper tracking I will file GitHub issues for the things I noted.