[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

How to properly define package-wide flags.

From: Benoit Sigoure
Subject: How to properly define package-wide flags.
Date: Thu, 16 Nov 2006 08:03:57 +0100
User-agent: Internet Messaging Program (IMP) H3 (4.0.2)

Hello folks,

In a recent discussion with Akim Demaille, we found out that we didn't set
our package-wide flags the same way and he couldn't convince me that his way
was safer/cleaner/etc so maybe you have an idea as to what's best practice:

My approach is to AC_SUBST([AM_*FLAGS], [-package-wide-flags]) in my

Akim's idea of AM_*FLAGS is that they are not meant to be defined in but in Makefile.ams. His approach is to AC_SUBST([MY_*FLAGS],
[-package-wide-flags]) and then have a (say at top-level) which
does AM_*FLAGS = $(MY_*FLAGS) and then include that everywhere it's

According to him, defining package-wide AM_*FLAGS could possibly clash with
that already defined in Makefile.ams. That's true but this would happen only
once (when adding the package-wide flags in the whereas with
his approach, the maintainer has to remember to include in every (which is annoying and error prone). He also argues that when
defining target_specific_*FLAGS, the corresponding AM_*FLAGS aren't
automatically included. Personally, I don't see the problem with it.

What do you think about this existential question?

SIGOURE Benoit aka Tsuna
  /EPITA\ Promo 2008, LRDE

reply via email to

[Prev in Thread] Current Thread [Next in Thread]