[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why forbidding "include" a sub-makefile.am with absolute path
|
From: |
Nick Bowler |
|
Subject: |
Re: why forbidding "include" a sub-makefile.am with absolute path |
|
Date: |
Mon, 29 Jun 2015 13:05:39 -0400 |
|
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On 2015-06-29 22:33 +0800, 赵峰(远猷) wrote:
> I find the following code in automake.
> >my $PATH_PATTERN = '(\w|[+/.-])+';
> ># This will pass through anything not of the prescribed form.
> >my $INCLUDE_PATTERN = ('^include\s+'
> > . '((\$\(top_srcdir\)/' . $PATH_PATTERN . ')'
> > . '|(\$\(srcdir\)/' . $PATH_PATTERN . ')'
> > . '|([^/\$]' . $PATH_PATTERN . '))\s*(#.*)?' . "\$");
>
> but why need forbidding "include" sub-makefile.ams with absolute path
> by the last line? In my Makefile.am, i need to include another
> sub-makefile from the path in a variable(ANOTHER_PJ_DIR) declared with
> AC_SUBET> Makefile.am
> > include @address@hidden
> the ANOTHER_PJ_DIR contains an absolute path of another project, but
> the include does't parsed by automake.How can i do it?thx!
> miles.zhaof
Configure substitutions (AC_SUBST) cannot work because Automake includes
are expanded only once, when Automake is run.
The generated Makefile.in file (which gets processed by configure) does
not contain the include commands at all.
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)