[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: SuSE and kdebug
From:       Mathias Kettner <kettner () suse ! de>
Date:       1999-04-29 7:54:31
[Download RAW message or body]

Hello,

As I understood NDEBUG, its behaviour should be:

 - Everything should work and compile, regardless,
   which packages are compiled with NDEBUG and 
   which not.

 - Exactly those application that are compiled
   without NDEBUG procude debugging information

 - Those applications that are compiled
   with NDEBUG should proced no debbuging information
   AT ALL. For a GUI application this means:
   nothing to stdout (cout), nothing to stderr (cerr).

For example: If kdelibs is compiled with NDEBUG, this should not mean,
that the general debugging system is turned of, but only, that there
should be no debugging message of kdelibs itself.

If ksomething is compiled without NDEBUG, it should print debbuging
output, regardless of kdelibs being compiled with NDEBUG or not.

Well, maybe you have another understanding of the flag NDEBUG. If
so, please tell me, and we will adapt our packages. Out aim ist:
No debbugging output for the user. Debugging output ist something
for developers. For users it is very confusing (as our supporters
can report...)



     Gruss,
        Mathias    .'\   /.               What do you think
                 .'.-.-'.-..              about compiling
            ..._:   .-. .-.   :_...       a 2.2.6 kernel?
          .'    '-.(o ) (o ).-'    .
         :  _    _ _~(_)~_ _    _  :
        :  /:   ' .-=_   _=-.    ;\  :
        :   :|-.._  '       _..-|:   :
         :   :| |:-:-.-:-:'| |:'   :
          .   .| | | | | | |.'   .'
            .   -:_| | |_:-'   .'
              -._   ``    _.-'
                  `-------''

[prev in list] [next in list] [prev in thread] [next in thread]