Re: automake breaks my file by putting includes after rules; how do I fix this?

[Jason Gross]

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
less about depending on automake than they did about depending on
autoreconf (I ended up setting up an extra branch of the source repo which
the autogenerated files get automatically pushed to); the intended
contributors/users of the source repo are mathematicians who may have
little to no programming experience.

-Jason


On Mon, Dec 2, 2013 at 8:10 AM, Gavin Smith <address@hidden>wrote:

> On Wed, Nov 20, 2013 at 9:33 PM, Jason Gross <address@hidden>
> 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
> > compile).  But this does not work with automake's generated all and
> all-am
> > targets, which compute their dependencies on the basis of the DATA
> > variable, which is auto-defined to be nobase_hott_DATA, which depends on
> > variables set in the included file.  How do I fix this?  (Should I
> submit a
> > bug report that includes should come before the autogenerated targets?)
> >
> Is it possible to use the "all-local" target to compile these files,
> and use another variable to list the files instead of DATA?
>