Installer log4cpp avec Homebrew, apk, dnf, MacPorts, Nix, apt, zypper

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• log4cpp-config

Historique du projet

The official project page says Bastiaan Bakker initiated coding on log4cpp in late 2000. SourceForge file metadata records the earliest old-file releases in December 2000, and the project page's release history shows a rapid 0.2.x and 0.3.x development period through 2002.

The project reached a stable 1.0 release in September 2007, then moved from CVS to Git with version 1.1.1 in November 2013. The official page says older pre-1.1.1 releases remain in CVS but that CVS is no longer maintained.

Development continued after a long mature-library period. The official release history lists 1.1.5 in December 2025 with CMake and modern Windows toolchain work, and 1.1.6 in March 2026 with enhanced CMake examples, CTest support, config.h generation, and compile-time stripping macros.

Historique d'adoption

log4cpp's own page points to availability in Debian stable, Ubuntu packages, and FreeBSD ports, and describes RPM support for building packages from the source tarball. The supplied package metadata also records availability in Homebrew, Alpine, Fedora/DNF, MacPorts, Nix, openSUSE/Zypper, Debian, and Ubuntu.

Its adoption pattern is typical for a C++ library: it is installed mostly as headers and libraries for programs that want log4j-like logging without adopting a larger framework. SourceForge download pages also show the maintained 1.1.x line alongside older 1.0.x, 0.3.x, and 0.2.x folders.

Modes d'utilisation

Applications include log4cpp headers, create or retrieve Category instances, attach appenders, and set priorities. The official examples demonstrate console, file, and rolling-file appenders, plus a properties-file workflow using `log4cpp::PropertyConfigurator::configure("log4cpp.properties")`.

Builders historically used autotools (`./configure`, `make`, `make check`, `make install`), while recent releases also support CMake, CTest, Visual Studio 2022 CMake projects, and RAD Studio 12.

Pourquoi les passionnés de paquets s'y intéressent

log4cpp is package-nerd interesting because it spans several eras of C++ packaging: SourceForge CVS tarballs, autotools releases, LGPL library packaging, distro development packages, a Git migration, and later CMake modernization. It is a small library, but one that reflects how long-lived C++ dependencies survive toolchain changes.

Chronologie

• 2000: log4cpp 0.0 and 0.1 artifacts appear on SourceForge; project coding was initiated in late 2000.
• 2001: log4cpp 0.2.x releases add packaging and platform support.
• 2002: 0.3.x development releases add threading, property configuration, rolling files, and Windows fixes.
• 2007: Stable 1.0 release.
• 2013: 1.1.1 release; project moves to Git.
• 2025: 1.1.5 release adds modern CMake and Windows build support.
• 2026: 1.1.6 release adds enhanced CMake examples, CTest support, and logging macros.

Related projects

• log4j: the Java logging API that inspired log4cpp's categories and appenders.
• log4c: a C logging framework in the same log4j-inspired family.
• log4cplus: another C++ logging implementation listed by the log4cpp project page.

Sources

• https://log4cpp.sourceforge.net/
• https://log4cpp.sourceforge.net/api/
• https://sourceforge.net/projects/log4cpp/files/
• source_facts.package-manager