I build log4cxx as a static library that I link into my own logging dll. In debug builds (on Windows using VC 2003) of my dll, I would get warnings complaining that the linker could not find the symbols database (*.pdb) for apr, apr-util and log4cxx. These were being produced but with their default name - vc70.pdb for each library. My solution was to have each library build their own pdb based on the libraries name. I also moved these output files to the same directory the lib files were being output to.
I'm not sure if this is something useful to the rest of the world. It saves me several hundred warning messages (and allows me to step into these libraries).
NamedPdbBuild.patch
Description: Binary data
