On 8/24/08, Wolfgang Bangerth <[EMAIL PROTECTED]> wrote: > We usually only link with external libraries because we believe that they > are well debugged, and because deal.II users do not call then directly (at > least that's the case with the ones we have currently). So as long as our > own functions that call the external libraries are correct, there never > was a reason to build external libraries in debug mode as well. > > So can you explain what your reason is to build them a second time, with > debug flags this time? I'm sure you have a good reason, I'm just curious > to hear what it may be :-)
True reason: I found out during time that even when I work with deal.II in debug mode, some bugs of my code succeed to "slip" thru the checkings or they cause faults before reaching deal.II interface. My impression is that bugs are found or debugged easier if selected underlying libraries could be put in dual (i.e. debug and production) mode too too. Especially this is true about the debug mode of STLport, which is truely paranoidal. More personal reason: In addition, my code is not always deal.II centric (although I never write without using deal.II), but I like to link external libraries by modifying Make.global_options. I wanted the process to become easier. As I wrote in the patch - the deal.II's assumption that the "outer world" is single versioned is not "fair". To fully support it will via the configuration process will be unnecessary cumbersome, but some things can be done. Thank you, regards, Dima. _______________________________________________
