From 6472da9bf4a1d02f9a700654b69c396556b6e1cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Oliver=20St=C3=B6neberg?= Date: Thu, 12 Dec 2024 13:47:28 +0100 Subject: [PATCH] readme.md: greatly updated packages section [skip ci] (#7091) --- readme.md | 24 +++++++++++++++++++++--- 1 file changed, 21 insertions(+), 3 deletions(-) diff --git a/readme.md b/readme.md index 45f256943f0..841b884bfb3 100644 --- a/readme.md +++ b/readme.md @@ -258,13 +258,31 @@ mv cppcheck cppcheck.exe ## Packages Besides building yourself on the platform of your choice there are also several ways to obtain pre-built packages.
-*Note:* The non-Windows packages are not maintained by the Cppcheck team but by the respective packagers instead. +Official packages maintained by the Cppcheck team: - (Windows) An official Windows installer is available via the official Cppcheck SourceForge page: https://cppcheck.sourceforge.io/. +- (Windows) Official builds of the current development versions are available via the [release-windows](https://github.com/danmar/cppcheck/actions/workflows/release-windows.yml) workflow. They are built nightly for the `main` branch and for each commit for release branches. As these are development versions please refrain from using these in production environments! + - A portable package (i.e. does not require installation) is available as the `portable` artifact. This is still a work-in-progress - see https://trac.cppcheck.net/ticket/10771 for details. + - An installer is available via the `installer` artifact. +- (Multi-Platform) A premium version with additional features provided by the original author of Cppcheck is available for purchase via https://www.cppcheck.com/. + +Unofficial packages *not* maintained by the Cppcheck team but their respective packagers: +- (Windows) An portable package is available via https://portableapps.com/apps/development/cppcheck-portable. +- (Windows / Outdated) A package is available via https://community.chocolatey.org/packages/cppcheck. +- (Windows / Outdated) A package is available via https://winget.run/pkg/Cppcheck/Cppcheck. +- (Windows / Outdated) A package is available via https://osdn.net/projects/sfnet_cppcheck/. - (Linux/Unix) Many major distros offer Cppcheck packages via their integrated package managers (`yum`, `apt`, `pacman`, etc.). See https://pkgs.org/search/?q=cppcheck for an overview. -- (Linux/Unix) Unless you are using a "rolling" distro, it is likely that they are not carrying the latest version. There are several external (mainly unsupported) repositories like AUR (ArchLinux), PPA (ubuntu), EPEL (CentOS/Fedora) etc. which provide up-to-date packages. -- (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. +- (Linux/Unix) Unless you are using a "rolling" distro, it is likely that they are not carrying the latest version. There are several external (mainly unsupported) repositories like AUR (ArchLinux), PPA (ubuntu), EPEL (CentOS/Fedora) etc. which might provide up-to-date packages. +- (Linux/Unix / Outdated) The Canonical Snapcraft packages (https://snapcraft.io/cppcheck / https://snapcraft.io/cppcheckgui) are unmaintained and contain very old (development) versions. Please refrain from using them! See https://trac.cppcheck.net/ticket/11641 for more details. - (MacOS) A package is available via Homebrew (`brew`). See https://formulae.brew.sh/formula/cppcheck#default. +- (Multi-Platform) A package is available via https://anaconda.org/conda-forge/cppcheck. +- Packages are also available from various download portals (mainly the Windows installer - sometimes re-packaged). + +*Note:* This is list is purely informational and listed in no particular order. + +*Note:* Please always try to obtain the package from the primary official source of your operating system/distro first and make sure you are getting the latest released version. + +*Note:* Some issues might be related to additional patches carried by the builds in these packages or the packaging itself. In that case issues might need to be reported to the respective project. ## Webpage