[Boost-users] boost logging from shared libraries

From: Austin Bingham (austin.bingham_at_[hidden])
Date: 2005-08-17 09:58:12

First, I wasn't sure where would be the most appropriate place to post
this question, so I apologize if it's gone to the wrong place.

I'm trying to figure out how to put logging statements in some shared
libraries which are then controlled via manipulate_logs() calls an the
executable that uses the libraries. It appears, after some rudimentary
experiments, that this does not work, and I was hoping to find out if
there is a way to do it.

The logging system, of course, does log manipulation using log names
and regular expression matching. As such, I assumed that logs were
statically allocated and, in some way, all registered with some
central registry which made them all available via their names.

Stepping through logging calls in the libraries seems to indicate that
logging code is being accessed and, as far as I can tell, the logs are
"enabled" and, in fact, trying  to log messages (to cout, for what
it's worth). However, I don't see anything printed except for log
messages genereted from the executable's source code.

So, is what I'm trying to do even feasible? I would love to be able to
have diagnostics built into my libraries which I could dis/enable as
necessary from the executive level. Hopefully I'm just missing
something simple. Thanks.
-- 
Austin Bingham
"If I were creating the world I wouldn't mess about 
with butterflies and daffodils. I would have started 
with lasers, eight o'clock, Day One!" 
Evil