These compiled files get distributed/installed, so I think they belong in
DATA.
The solution I ended up using was manually including an all-am target
below the definition, which overrides the one that automake generates.
I think the other contributors to the project would complain only slightly
On Mon, Dec 16, 2013 at 3:49 PM, Jason Gross jasongro...@gmail.com wrote:
These compiled files get distributed/installed, so I think they belong in
DATA.
The solution I ended up using was manually including an all-am target
below the definition, which overrides the one that automake
Subject: Re: automake breaks my file by putting includes after rules;
how do Ifix this?
Message-ID:
CAKObCarF2TYNTkDRJHvNNeP_Who6CbcqbGa4gncOOVXT=zk...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
These compiled files get distributed/installed, so I think
On Wed, Nov 20, 2013 at 9:33 PM, Jason Gross jasongro...@gmail.com wrote:
I have a Makefile.am which includes another file in order to get a list of
files it should compile (I don't want to require running autoreconf and
configure whenever you add a file that the makefile already knows how to
I have a Makefile.am which includes another file in order to get a list of
files it should compile (I don't want to require running autoreconf and
configure whenever you add a file that the makefile already knows how to
compile). But this does not work with automake's generated all and all-am
On Wed, Nov 20, 2013 at 9:33 PM, Jason Gross jasongro...@gmail.com wrote:
(I don't want to require running autoreconf and
configure whenever you add a file that the makefile already knows how to
compile).
You actually do not need autoreconf. Maintainer mode will take care of it
for you buy
