[Log4cpp-devel] PropertyConfigurator from within library?

[Scott M <sm...@ya...>]

I'm building a library (UNIX .so, but that shouldn't matter) which uses
log4cpp. Clearly I want my library to work with old apps which don't use
log4cpp, as well as new log4cpp-based apps.

How do I configure log4cpp for my library? I'd like to have a separate
lib.conf file, which I load at lib load time. Problem is it looks like
PropertyConfigurator is static (global) per process, so any other libraries
or the app itself has the potential of overwritting my settings. Is this
true?

Do multiple PropertyConfigurator::configure() calls (within the same
process) complement each other? That is, they are additive, so each
component can configure itself without fear of corrupting other components'
log4cpp setup?

Thanks,

- Scott

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com