Stephan Assmus wrote:
Bruno Albuquerque wrote (2008-01-31, 13:29:52 [+0100]):Jérôme Duval wrote:Hi Bruno, 2008/1/31, Bruno Albuquerque <bga@xxxxxxxxxxxxx>:Any ideas why this is failing with DEBUG enabled but not in a normal build? I did take a look around to see if I could figure it out but i didn't find anything obvious.There is a macro replacing this function when __OPTIMIZE__ is not defined. The actual function can be found insrc/system/libroot/posix/glibc/ctype/ctype_l.c Maybe try to include it in src/system/libroot/posix/glibc/ctype/Jamfile.Not that easy it seems. Lots of undefined stuff in ctype_l.c.Anyway, a follow-up question. Is there any way to indicate to the build system that I want to build debug versions of mail_daemon, it's add-ons and libmail.so without having the build system to compile all dependencies in debug mode?There is a description in UserBuildConfig.sample, don't know if it is what you need:# Set the debug level for file src/bin/gdb/gdb/haiku-nat.c (note, that # the object file must be specified) to 1. It is worth mentioning, that the # executable the object file is linked into (gdb), will still be placed in # generated/objects/.../release/... Only when setting DEBUG for the # executable, too, it will be placed in .../debug_1/... DEBUG on <src!bin!gdb!gdb!>haiku-nat.o = 1 ;
I saw this, but this is per object file (and there are dozens of related object files). A way to selectively set debug mode for a specific library, binary or add-on is what I am looking for.
Thanks anyway. -Bruno