log4cplus is a simple to use C++ logging API providing thread-safe, flexible, and arbitrarily granular control over log management and configuration. It is modelled after the Java log4j API.
Agree with kyberuserid..., I used this API in a project with hopes that it would simplify my task of development, but it didn't... Worked in native win32/x64 version of the application that uses it, but when called from managed code that uses the native version of application dll it throws scheduler_resource_allocation_error. So I'm going to consider looking for something else, maybe Pantheios - I'm back to square one after all that bloody hard work only to discover that I can't make a release because it fails with .NET
I compile static lib with my project (Visual Studio 2010), but linking error! --------------------------------------------------------------------------- 1>ClCompile: 1> All outputs are up-to-date. 1>ManifestResourceCompile: 1> All outputs are up-to-date. 1>log4cplusSD.lib(factory.obj) : error LNK2019: unresolved external symbol "public: __thiscall log4cplus::SysLogAppender::SysLogAppender(class log4cplus::helpers::Properties const &)" (??0SysLogAppender@log4cplus@@QAE@ABVProperties@helpers@1@@Z) referenced in function "public: virtual class log4cplus::helpers::SharedObjectPtr<class log4cplus::Appender> __thiscall log4cplus::spi::FactoryTempl<class log4cplus::SysLogAppender,class log4cplus::spi::AppenderFactory>::createObject(class log4cplus::helpers::Properties const &)" (?createObject@?$FactoryTempl@VSysLogAppender@log4cplus@@VAppenderFactory@spi@2@@spi@log4cplus@@UAE?AV?$SharedObjectPtr@VAppender@log4cplus@@@helpers@3@ABVProperties@53@@Z) 1>D:\Projects\AutoTradeSystem\Bin\Win32\Debug\Backtest.exe : fatal error LNK1120: 1 unresolved externals 1> 1>Build FAILED.
I hate this ugly piece of crap. Was going to use it on Windows because log4cpp doesn't work there and logcxx is an overblown monster. This one is especially nasty having absorbed a welter of ugly hacks over the decade since the original author jettisoned it. The hacks are totally undocumented and the most you can find are amateurish write-ups at random web pages. Usable but only by painful reading of its sources and inference of what a c++ log4j is supposed to be doing. Says more about C++ than I ever could with words. Decided to just gut the whole thing and roll my own simple sprintf based logger in disgust.