Hi,
Is it still possible to compile out debugging messages? According to http://winehq.org/site/docs/winedev-guide/dbg-compiling, I can pass --disable-debug, but the Changelog says that option was removed about 10 month ago.
- Lei
Also, the patch from 2007/04/17 only removed -DWINE_NO_DEBUG_MSGS / -DWINE_NO_TRACE_MSGS from configure, but not from include/wine/debug.h.
On 2/12/07, Lei Zhang thestig@google.com wrote:
Hi,
Is it still possible to compile out debugging messages? According to http://winehq.org/site/docs/winedev-guide/dbg-compiling, I can pass --disable-debug, but the Changelog says that option was removed about 10 month ago.
- Lei
Lei Zhang wrote:
Also, the patch from 2007/04/17 only removed -DWINE_NO_DEBUG_MSGS / -DWINE_NO_TRACE_MSGS from configure, but not from include/wine/debug.h.
Right, it was a problem with a lot of people turning debug messages off and sending in useless problem reports. So that option got removed from configure. There is one valid reason to turn debugging off and that is to cross check that there are no side effects hidden in some debug message.
On 2/12/07, Lei Zhang thestig@google.com wrote:
Hi,
Is it still possible to compile out debugging messages? According to http://winehq.org/site/docs/winedev-guide/dbg-compiling, I can pass --disable-debug, but the Changelog says that option was removed about 10 month ago.
bye michael
On 2/12/07, Michael Stefaniuc mstefani@redhat.com wrote:
Lei Zhang wrote:
Also, the patch from 2007/04/17 only removed -DWINE_NO_DEBUG_MSGS / -DWINE_NO_TRACE_MSGS from configure, but not from include/wine/debug.h.
Right, it was a problem with a lot of people turning debug messages off and sending in useless problem reports. So that option got removed from configure. There is one valid reason to turn debugging off and that is to cross check that there are no side effects hidden in some debug message.
On 2/12/07, Lei Zhang thestig@google.com wrote:
Hi,
Is it still possible to compile out debugging messages? According to http://winehq.org/site/docs/winedev-guide/dbg-compiling, I can pass --disable-debug, but the Changelog says that option was removed about 10 month ago.
bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Sr. Network Engineer Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani@redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart
Well, we should update the documentation either by removing section 2.6 or mention passing -DWINE_NO_{DEBUG/TRACE}_MSGS instead.
Lei Zhang wrote:
On 2/12/07, Michael Stefaniuc mstefani@redhat.com wrote:
Lei Zhang wrote:
Also, the patch from 2007/04/17 only removed -DWINE_NO_DEBUG_MSGS / -DWINE_NO_TRACE_MSGS from configure, but not from include/wine/debug.h.
Right, it was a problem with a lot of people turning debug messages off and sending in useless problem reports. So that option got removed from configure. There is one valid reason to turn debugging off and that is to cross check that there are no side effects hidden in some debug message.
On 2/12/07, Lei Zhang thestig@google.com wrote:
Hi,
Is it still possible to compile out debugging messages? According to http://winehq.org/site/docs/winedev-guide/dbg-compiling, I can pass --disable-debug, but the Changelog says that option was removed about 10 month ago.
Well, we should update the documentation either by removing section 2.6 or mention passing -DWINE_NO_{DEBUG/TRACE}_MSGS instead.
Removing that part of the documentation is probably best. Somebody really wanting to disable that will figure it out for himself.
bye michael
-
Lei Zhang -
Michael Stefaniuc