Let me think about this some more...

On Dec 17, 2007 8:58 AM, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote:
> Mike Emmel wrote:
> > I was wondering of we could make this change
> >
> > diff --git a/configure.in b/configure.in
> > index 2349cec..67db470 100644
> > --- a/configure.in
> > +++ b/configure.in
> > @@ -365,9 +365,6 @@ AC_ARG_ENABLE(debug,
> >    enable_debug=no)
> >  if test "$enable_debug" = "yes"; then
> >      CFLAGS="$CFLAGS -g3 -fno-inline"
> > -    DIRECT_BUILD_DEBUG=1
> > -else
> > -    DIRECT_BUILD_DEBUG=0
> >  fi
> >
> >
> > We have another flag --enable-debug-support
> >
> > So the combination --enable-debug --enable-debug-support get the full
> > debug version while --enable-debug will just get the standard C symbol
> > debug.
>
> --enable-debug-support does not enable debug messages in libdirectfb, but
> builts the necessary code into libdirect to do debug builds of other 
> libraries,
> e.g. libdirectfb or external libraries.
>
> --enable-debug was used to enable expansion of debug macros in libdirect,
> libfusion and libdirectfb code, in addition to CFLAGS changes.
>
> But I understand that setting the compiler flags should be separate, either
> by setting them from outside (CFLAGS=-g3 ./configure) or by adding another
> parameter.
>
> > The reason is I'm seeing some problems that may potentially be related
> > to C++ and the enhanced debug support.
> > I've made this change locally for various other reasons in the past.
>
> Compiler issues with the macros?
>
> --
> Best regards,
>   Denis Oliver Kropp
>
> .------------------------------------------.
> | DirectFB - Hardware accelerated graphics |
> | http://www.directfb.org/                 |
> "------------------------------------------"
>

_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to