[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: building directly from $(top_builddir)
From: |
Bruno Haible |
Subject: |
Re: building directly from $(top_builddir) |
Date: |
Sat, 18 Jul 2009 18:06:54 +0200 |
User-agent: |
KMail/1.9.9 |
Eric Blake wrote:
> gnulib-tool could make this part easier by automating it somehow (a new
> command line option to state whether the gnulib.mk fragment will be used
> in the current directory [default], or included from some other directory
> where all relative paths need an extra prefix [as in bison's case]).
Such a feature would require changes (to insert $prefix here and there) in
many places, i.e. in many module descriptions. That's hardly maintainable
(and rarely tested, since most gnulib users would not use this feature).
The alternative quite easy: Just include a tiny Makefile.am in the
subdirectory, that does
include gnulib.mk
and invoke that Makefile from the top-level directory, by use of
AC_CONFIG_SUBDIRS.
Does bison have any specific problems following this approach that
everyone else has used so far?
Bruno
- Re: Help with create_pipe_bidi, Eric Blake, 2009/07/18
- new module pipe-filter, Bruno Haible, 2009/07/19
- Re: new module pipe-filter, Bruce Korb, 2009/07/21
- Re: new module pipe-filter, Paolo Bonzini, 2009/07/21
- Re: new module pipe-filter, Bruno Haible, 2009/07/21
- Re: new module pipe-filter, Paolo Bonzini, 2009/07/21
- Re: new module pipe-filter, Paolo Bonzini, 2009/07/22
- Re: new module pipe-filter, Bruce Korb, 2009/07/31