On 1/14/10 7:28 AM, Daniel Pocock wrote:
This is how I've been going about it: create $(top_srcdir)/ganglia.inc
like so:
FIXCONFIG = $(top)/scripts/fixconfig
You probably mean $(top_builddir)
%: %.tmpl $(FIXCONFIG)
$(FIXCONFIG) $
AFAIU, %: %.tmpl is GNU Make specific and won't work
Hi,
I've been working on a project, Ganglia, that is built with autotools
Included in the source tree are templates for various configuration
files (e.g. modpython.conf.in). Some of these include hard coded paths.
It seems appropriate to replace the hardcoded paths with substitutions
Daniel Pocock wrote:
Therefore, I felt that I should be aiming to have the config files
generated at the last moment - probably during `make install', just
before they are installed. Can anyone suggest best practice for doing
this?
please refer to
Peter Johansson wrote:
Daniel Pocock wrote:
Therefore, I felt that I should be aiming to have the config files
generated at the last moment - probably during `make install', just
before they are installed. Can anyone suggest best practice for
doing this?
please refer to
Daniel Pocock dan...@pocock.com.au writes:
Thanks for that - the sed example appears to be the type of thing I want.
However, is there a more concise way to do this? I was thinking there may
be some way to invoke sed or m4 on a template in much the way that gcc is
invoked for *.c
Half of
Russ Allbery wrote:
Daniel Pocock dan...@pocock.com.au writes:
Thanks for that - the sed example appears to be the type of thing I want.
However, is there a more concise way to do this? I was thinking there may
be some way to invoke sed or m4 on a template in much the way that
