Hi,
I have this snippet in my 'Makefile.am'
include am/test_data.am
$(srcdir)/am/test_data.am: $(srcdir)/test/data.txt
$(srcdir)/am/test_data.am.in
cd $(srcdir) $(SHELL) bootstrap am/test_data.am
It first includes (at Automake time) a snippet, which is generated while
bootstrapping.
Hello automakers!
I'm using autoconf 2.69 and automake 1.11.6 (Debian 7 stable). Recently I tried
defining the source code folder name using a variable and strange things happen.
I'm not sure whether this is a bug or my mistake. Here's the revelant part
from Makefile.am, before the change, which
On 2014-08-12
Nick Bowler nbow...@elliptictech.com wrote:
Yes, but I think you have clean/distclean backwards. There are four
clean targets:
mostlyclean
clean
distclean
maintainer-clean
Each target in the list performs all the actions of the targets
above it in addition to
On 2014-08-12
fr33domlover fr33domlo...@riseup.net wrote:
Hello,
I'm writing a Makefile.am with a custom piece for building, distributing and
installing Doxygen-generated documentation. All the generated files are used
as values for the special-scheme variables, e.g. 'dist_reference_DATA
On Sun, 17 Aug 2014, fr33domlover wrote:
Why does it happen? Is this a known problem? I didn't find any material on
the web. Of course I can move the definition of src to configure.ac, but I'd
like to know what I'm missing (or is it a bug).
Automake does not support Make-style computations of
On Tue, Aug 12, 2014 at 4:10 PM, Wookey woo...@wookware.org wrote:
As porting work (for arm64) recently I have done a lot of fixing up
packages to run autoreconf on build as this is the only way to ensure
that their config.sub/guess and libtool files are up to date for
architectures released
On 08/18/2014 03:07 AM, fr33domlover wrote:
Anyone has some advice? My code uses those targets at the moment, but I'm not
sure it's good for long term.
Not sure I understand your problem, but have you read the 'Extending'
section in the manual
