I'm working on making network support in Log4cxx optional so that if you don't need it, you don't need to build a binary with those classes in it. This reorganization also means that the network backend is not limited to just APR, but it can be Boost instead.
I'm now coming up with the question of what should we do with these classes if support is disabled? Currently things like the NTEventLogAppender are just #defined out, but the header is still installed even on Linux and OSX. The class can't be initialized from the config file as it is not registered. The options are: 1. Install the headers regardless, but the code in the .cpp file is #defined out(what the NTEventLogAppender does) 2. Only install the needed headers The disadvantage to #1 is if you are configuring Log4cxx manually for some reason, the headers will still be available and you won't get a compiler error when you build, but a linker error. Option #2 would cause a compiler error, but is not what we have been doing before. -Robert Middleton
