pkg.sopackage field notes

brew / rank 4258

Install log4cpp with Homebrew

Configurable logging for C++. Version 1.1.6 via Homebrew; verified 2026-07-24.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install log4cpp

provider-native install command

overview

Package summary

Configurable logging for C++

Commands and aliases

  • log4cpp-config

history

Project history and usage

log4cpp, officially also called Log for C++, is a C++ logging library modeled after log4j. It provides categories, appenders, layouts, properties-based configuration, file and syslog logging, and optional integrations such as IDSA.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
log4cpp-configexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version1.1.6
manager updated2026-07-24
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:log4cpp
Version1.1.6
Package managerHomebrew
Homepagehttps://log4cpp.sourceforge.net/
Last updated2026-07-24T15:58:49+02:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • curated package history
  • pkgdb category and tag curation