Re: gnome-common/macros2 cleanup
- From: James Henstridge <james daa com au>
- To: Havoc Pennington <hp redhat com>
- Cc: desktop-devel-list <desktop-devel-list mail gnome org>
- Subject: Re: gnome-common/macros2 cleanup
- Date: Tue, 11 Feb 2003 23:49:53 +0800
Havoc Pennington wrote:
On Tue, Feb 11, 2003 at 11:19:58PM +0800, James Henstridge wrote:
Based on this, the only macros I would consider worth keeping in
gnome-common are:
* GNOME_COMPILE_WARNINGS
I think we should try to get this one in the autoconf distribution.
"Turn on the best-practices set of warnings for the current compiler"
* GNOME_DEBUG_CHECK
I'm not sure this is really useful, I would just let modules do their
own thing. For example metacity has --enable-verbose and so forth.
But if it is useful, again it belongs in autoconf.
The common autogen.sh script could probably do with a bit of a cleanup.
The main one is to allow modules to select an autoconf version other
than automake-1.4. While you might consider this unnecessary if we
standardise on a single automake version, it will help during
transition.
I agree you should able to select your autoconf/automake version.
(Not that it does us any good until someone fixes scrollkeeper/etc.
rules to pass distcheck with new automake)
according to the docs of automake-1.7.2, you can customise the check
used to check for files not removed by "make uninstall". Maybe this
should be used to handle scrollkeeper? I have some patches pending to
help simplify gtk-doc build infrastructure which should help here too.
James.
--
Email: james daa com au
WWW: http://www.daa.com.au/~james/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]