If you are looking for sample code to show you have to use log4cplus, go here.
The purpose of this project is to port the excellent Log for Java (log4j) logging library to C++.
This project is now in "Production" status.
Please feel free to contact me if you have any questions or if you would like to help the project: wilx@users.sourceforge.net.
If you want to get help with log4cplus use or compilation or if you have any other problem with it, please use the tracker or the log4cplus-devel mailing list. For bug reporting instructions see Bug Reporting Instructions down below.
This is the current road map:
| Release | Date | Additional Functionality | Status |
|---|---|---|---|
| 2.0.0 | C++11 only | Planning | |
| 1.2.0 | Planning | ||
| 1.1.1 | February 2013 May 2012 |
Unintrusive improvements and bug fixes relative to 1.1.0. See ChangeLog for a detailed list of changes. | Released |
| 1.1.0 | September 2012 October 2012 |
AsyncAppender, Log4jUdpAppender,
SysLogAppender with remote syslog UDP logging
support enabled on Windows, Qt4DebugAppender,
simple C interface for interoperability with C,
inter–process file locking to file appenders to allow
logging into a single log file from multiple processes, Mapped
Diagnostic Context (MDC), alternative thread identification
(%T) converter to pattern layout, function name
converter (%M), wchar_t
↔ char conversion implementations based on
standard C locale functions and based on iconv(),
DeviceAppender to allow use of Boost.IOStream's Sink as
appender, LOG4CPLUS_*_FMT() macros to allow printf-like
formatted output where it is possible (requires variadic macros
support). |
Released |
| 1.0.4.2 | October 2012 December 2012 |
Maintenance release. | Released |
| 1.0.4.1 | April 2012 | Bug fixing release. | Released |
| 1.0.4 | October 2010 January 2011 |
Released | |
| 1.0.3 | February 2009 March 2009 |
Win32DebugAppender |
Released |
The log4cplus 1.1.1 has been released. There are both bug fixes and small new features relative to 1.1.0. Please see ChangeLog or log4cplus 1.1.x branch changes for detailed list of changes.
The log4cplus 1.1.1-RC4 has been released. This is mostly a bug fix release but there are also some small new features.
The log4cplus 1.0.4.3 has been released. This is a maintenance release with only two Solaris compatibility fixes without any functional changes.
The log4cplus 1.1.1-RC3 has been released. It contains more fixes related to portability to MinGW and most importantly, a fix to broken Windows builds.
The log4cplus 1.1.1-RC2 has been released. It contains some bug fixes and small improvements cherry-picked from trunk branch.
The log4cplus 1.0.4.2 has been released. This is a maintenance release with only a handful of compatibility fixes without any functional changes.
The log4cplus 1.1.1-RC1 has been released. It contains some bug fixes and small improvements cherry-picked from trunk branch.
The log4cplus 1.1.0-RC10 has been released. This is branch 1.1.x release with bug fixes and some other improvements.
The log4cplus 1.0.4.2-RC1 has been released. This is a maintenance release with only a handful of compatibility fixes without any functional changes.
The log4cplus 1.1.0-RC9 has been released. This is branch 1.1.x release with bug fixes.
The log4cplus 1.1.0-RC8 has been released. This is branch 1.1.x release with bug fixes as well as new features.
The log4cplus 1.1.0-RC7 has been released. This is branch 1.1.x release with bug fixes as well as new features.
The log4cplus 1.1.0-RC6 has been released. This is branch 1.1.x release with bug fixes as well as new features.
The log4cplus 1.0.4.1 has been released. This is a bug fix release. This is likely the last release from 1.0.x code base. Further releases will be based on trunk and 1.1.x branches.
I have only recently realized that log4cplus is being used wider than I thought. The most important (in my eyes) piece of software that I have recently discovered using log4cplus is BIND 10. This led me to realization that I need more information about log4cplus' users and uses. Thus I would like to ask you for feedback about log4cplus. Feel free to post answers to following questions to mailing list or privately to myself:
The log4cplus 1.0.4.1-RC2 has been released. This is a bug fix release.
The log4cplus 1.1.0-RC5 has been released. This is branch 1.1.x release with small amount of changes relative to 1.1.0-RC4.
The log4cplus 1.1.0-RC4 has been released. This is branch 1.1.x release.
The log4cplus 1.1.0-RC3 has been released. This is branch 1.1.x release.
The log4cplus 1.1.0-RC2 has been released. This is trunk development release.
The log4cplus 1.1.0-RC1 has been released. This is trunk development release.
The log4cplus 1.0.4.1-RC1 has been released. This is a bug fix release.
The log4cplus 1.0.4 has been released. This is a bug fix release. See release notes for full list of changes since 1.0.3.
The log4cplus 1.0.4-RC11 has been released. This is a bug fix release. See release notes for details.
The log4cplus 1.0.4-RC2 has been released. This is a bug fix release. See release notes for details.
The log4cplus 1.0.3 has been released. Many bugs have been fixed in this release. See the list of closed bugs in project's bug tracker and change log for details.
The 1.0.3-RC8 is the last release candidate before the real 1.0.3 release. The 1.0.3 release will be the last release from the 1.0.x series.
log4cplus is a simple to use C++ logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modeled after the Java log4j API.
This is a "bug fix" release. No significant functionality has been added.
For successful resolution of reported bugs, it is necessary to provide enough information:
CMAKE_* variables valueswchar_t or not