IMHO, for LOG4CXX_DEBUG-type macros, it's difficult(impossible?) to
dump a string object without calling c_str(). A good news is that most
of the std::string implementations of c_str() seem to be efficient.
BTW, I'd like to share some information of log4cxx we got. Because we
care about performanc
JK,
Make sure in your linking that you are referencing the object archive
and not the shared object. I think you need to use -Bstatic before the
-lapr and -lapr-util in order for it to pick up the archives. Make sure
that the libapr.ar and libapr-util.ar files are in the same places as
the .so f
hi , I am newbie to log4cxx. recently I am trying to use log4cxx in
my project to take place of my owner loger mechanism. but I feels some
drawbacks on it. for example.
mylog. log(__FILE__,__LINE__,"%s%d", "str ", 1000").
I can easily print runtime of str , 1000 with one statement. it's my
o
As far as I know, in *nix-like systems, library tool such as "ar" may
be used to combine several libraries together.
Lingyun Tuo
On 1/4/06, Jitendra Kharche <[EMAIL PROTECTED]> wrote:
>
> Hi Lingyun,
>
> Thanks for the reply. But there is some more help required.
> We could also build Log4cxx sta
Hi Lingyun,
Thanks for the reply. But there is some more help required.
We could also build Log4cxx statically but the static log4cxx library
links apr & apr-util dynamically. So when we build our application, it
needs apr & apr-util libraries. We want to avoid shipping these
binaries. We want t
