[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Developer_CFLAGS
From: |
Ben Pfaff |
Subject: |
Re: Developer_CFLAGS |
Date: |
Tue, 11 Nov 2008 20:54:00 -0800 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) |
John Darrington <address@hidden> writes:
> On Tue, Nov 11, 2008 at 07:52:20PM -0800, Ben Pfaff wrote:
> John Darrington <address@hidden> writes:
>
> > On Tue, Nov 11, 2008 at 07:08:44AM -0800, Ben Pfaff wrote:
> > John Darrington <address@hidden> writes:
> >
> > > Can anyone suggest an appropriate way in which we can set some
> > > additional CFLAGS which are seen by developers, but not in
> tarballs
> > > intended for the general public?
> >
> > Add an "--enable-developer-mode", I guess? (We already have
> > something like that for --with-gui-tools, right?)
> >
> > > Eg: -DGDK_MULTIHEAD_SAFE=1 etc.
> >
> > What does that do?
> >
> > It disables certain parts the the API which might cause problems when
> > running applications on a system with more than one display.
>
> Can you explain why we would want that for developers but not for
> users?
>
> I guess it was a bad example. GDK_DISABLE_DEPRECATED is probably a
> better example.
I can't find any documentation for that, but it seems to #ifdef
out prototypes for functions that are deprecated. If that is so,
then I guess we could add a --disable-deprecated-apis or some
such. Or you could just specify it at configure time:
./configure CPPFLAGS=-DGDK_DISABLE_DEPRECATED.
--
Ben Pfaff
http://benpfaff.org