Message: 4
Date: Wed, 10 Dec 2008 07:39:04 +0100
From: Ralf Wildenhues [EMAIL PROTECTED]
Subject: Re: GNU Make Extensions
To: Tom Browder [EMAIL PROTECTED]
Cc: automake@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Hello Tom,
* Tom Browder wrote on Wed, Dec
From: Ralf Wildenhues [EMAIL PROTECTED]
Wow. It would be interesting to see how much faster things get with the
chances. Are the libraries all created with libtool? Because then I
guess they will end up being the remaining bottleneck (that would be
interesting to see, too).
If interested,
Is there a good/easy/maintainable way to set the same CFLAGS/CPPFLAGS
for the entire project except for one specific subtree?
I'm using a recursive automake build where a few flags are default
set by configure (e.g. overrides the default -O2 -g to different
flags). I'd like to enable
Counterproductive presumptuous flamings aside, there are compelling
arguments on both sides of the issue for having or quelling verbose
compilation output. Depending on at least the development
environment, requirements, expectations, and values of the
developers, I've been in situations
Ralf Corsepius [EMAIL PROTECTED] wrote:
scripts that give you information like includes, libraries,
etc... is there
some autoconf/automake/other magic i can use to automatically
generate one
of these for my distribution?
Nope. Such *-config scripts are ordinary, manually written
Date: Mon, 24 Apr 2006 23:29:34 +1000
From: Brendon Costa [EMAIL PROTECTED]
Subject: Re: Reducing verbosity of automake
To: automake@gnu.org, Brendon Costa [EMAIL PROTECTED]
All patches I've seen add quite a bit of bloat to Makefile.in's, for
dubious value (remember the compile rules may be
, 2005 at 01:42:19PM -0400, Christopher Sean Morrison
wrote:
AM_INIT_AUTOMAKE
...
AM_INIT_AUTOMAKE([no-dependencies])
I think that this option tells automake to generate different
Makefile.in,
which is horter and doesn't include the code for dependency tracking
Hello,
I've have a section in a configure.ac that attempts to dynamically
determine whether or not to enable dependency tracking and it seems to
be causing quite a bit of hassle on at least some versions of automake.
Basically, I have the following:
AC_MSG_CHECKING([whether dependency
Thanks for the tip and it does look useful, though that doesn't affect
whether or not all compilations are run through depcomp does it? Our
non-CVS source distributions are easily treated as static sources that
won't change much beyond simple build tweaking and minor bug fixing.
So the extra
