Re: Re: why forbidding "include" a sub-makefile.am with absolute path

[Bert Wesarg]

On Tue, Jun 30, 2015 at 2:16 AM, 远猷 <address@hidden> wrote:
> thanks for your reply!
>
> but why forbidding “include” a sub-makefiles.am with absolute path?

Do you want to 'include' a 'automake file' fragment so that it is
processed when automake is running (mostly done by autoreconf these
days) or do you want to include a 'make file' fragment, which is
processed when make is run?

You are speaking about 'sub-makefiles.am' above, which indicates the
former. While your 'common.mk' indicates the latter.

To your question at hand, if you have an absolute path to an 'automake
file' in an Automake include directive, than this would mean, you are
the only person who can run automake in this project.

If you want to include a 'make file' at make time, than I suggest you try this:

@AMDEP_TRUE@@am__include@ @am__quote@@address@hidden@am__quote@

Now automake generates a include statement which will be processed at make time.

HTH,
Bert