symbols and no optimization for external libs in dgbutil builds?

[Michael Stahl]

On 19/04/13 02:00, Markus Mohrhard wrote:
> Hey,
> 
> is there anything speaking against building external libraries in the
> dbgutil case with symbols and without optimization? Ideally IMHO we
> should even build c++ libraries with GLIBCXX_DEBUG.

we should definitely build everything with debug symbols in a dbgutil
build.  i don't really have an opinion on optimizations.

we already build the 2 externals where it matters (cppunit/liborcus)
with _GLIBCXX_DEBUG; i'd say it's probably a good idea to use it for all
externals but in case a library has never been build with it we should
be prepared to patch some issues in it, i.e. it needs testing.

there are also more debug modes in some externals, similar to our own
--enable-dbgutil with additional assertions; there may be some among
them that make sense to enable but there are probably others that don't
make sense, e.g. iirc there was some XML library that dumps out every
element it parses on stderr which is a bit too much verbosity.

for example python has --with-pydebug, which we actually use currently
when building against MSVC debug runtimes but not on other platforms.