I'm investigating the posibility of using log4cxx in a middleware product - the Java port of which already uses log4j. As we ship on numerous platforms and because of the fact that we provide libraries which our customers link with, we have to make as few assumptions about customer code as possible. In particular we cannot make assumptions about customer use of classic or standard iostreams (shipping two versions of libraries is not an option). Unfortunately there is extensive use of iostreams in log4cxx which would be a show stopper for using it (for us that is).
Could you not go with standard iostreams for log4cxx then? I mean, given that iostreams tend to be entirely in headers, it seems like you could compile log4cxx with an iostreams library independant of what your customers have.
--Chris
