Curran Schiefelbein wrote: > Bart Samwel wrote: >> As I said earlier, it's the switch on the C++ compiler that matters (to >> be precise, the _DEBUG preprocessor define)! > > Crumbs. I was hoping I could get more *nix like behavior -- if you don't > want debugging symbols in everything, you don't have to have them, but > you can still have them in your own code. > > The shared dependency on MSVC runtime libs is a good reason not to do > that, though. Thanks!
Note: you _can_ build the libraries without debug info, but you'd have to tweak the makefiles yourself to remove the "debug info" flags. Note that in VC++ the debug info does NOT add to your final executable size, it's stored in a PDB file that is separate from your executable. Therefore, the traditional UNIX reason for not including debug info does not apply. > (Are there possibly MSVC-built libs that are agnostic about debug vs. > release MSVC libs? I could swear I've linked against release libraries > in a Debug progam in past work... but they might have been debug libs > masquerading as release ones.) It's not a problem if you link against DLLs, as long as the interfaces are well-defined and C-only, and if you don't have free memory allocated by the library or vice versa. This doesn't work for libpqxx, because it is a C++ library. Libpqxx can definitely link against a release mode libpq, but we decided against that because of the configuration complexity this entails. Cheers, Bart _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
