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

2015-06-30 Thread Bob Friesenhahn
On Tue, 30 Jun 2015, 远猷 wrote: thanks for your reply! but why forbidding “include” a sub-makefiles.am with absolute path? Automake projects are expected to be self-contained and not refer to anything outside of the package. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.si

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

2015-06-29 Thread Bert Wesarg
On Tue, Jun 30, 2015 at 2:16 AM, 远猷 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

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

2015-06-29 Thread 远猷
thanks for your reply! but why forbidding “include” a sub-makefiles.am with absolute path? from Alimei-Android--发件人:Nick Bowler日 期:2015年06月30日 01:05:39收件人:赵峰(远猷)抄 送:automake主  题:Re: why forbidding "include" a sub-makefile.am with

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

2015-06-29 Thread Nick Bowler
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 . ')' >