Hello Peter,
* Peter Johansson wrote on Sat, Feb 12, 2011 at 09:56:41PM CET:
> I got bitten by how VPATH builds work and wondered if there is a
> good way to avoid getting bitten again.
Not an easy question.
> I have an Automake snippet (see below) that creates a file,
> `.revision', with curren
Hello Ralf,
* Ralf Hemmecke wrote on Sat, Feb 12, 2011 at 11:46:55PM CET:
> I've a project that must use subdir-objects, because of filename
> clashes in subdirectories (non-recursive build).
> The generated Makefile contains a target "mostlyclean-compile" which
> has about 1500 lines that look l
I've a project that must use subdir-objects, because of filename clashes
in subdirectories (non-recursive build).
AM_INIT_AUTOMAKE([-Wall -Werror foreign subdir-objects])
I just have
lib_LTLIBRARIES = libfoo.la
check_PROGRAMS = ${TESTSUITE_TESTS} ${TESTSUITE_XFAIL_TESTS}
but quite a lot of fi
Hello;
I got bitten by how VPATH builds work and wondered if there is a good
way to avoid getting bitten again.
I have an Automake snippet (see below) that creates a file, `.revision',
with current revision number and from this is a C header file
`revision.h' created. Then to test that thing
> From: automake-bounces+jeff.daily=pnl@gnu.org
> [automake-bounces+jeff.daily=pnl@gnu.org] On Behalf Of Ralf Hemmecke
> [hemme...@gmail.com]
> Sent: Friday, February 11, 2011 11:18 AM
> To: automake@gnu.org
> Subject: Test support for automake
>
> I have a non-recursive Makefile.am with
I have a non-recursive Makefile.am with which I build a library foo. I
list all my tests (quite a lot) in check_PROGRAMS.
All those tests should (of course) get libfoo.la as LDADD, but how
exactly do I do that _without_ doing a per-target *_LDADD specification.
Per target specification sounds
