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
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
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 . ')'
>
Hi guys,
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\)/'
於 一，2015-06-29 於 10:00 +0200，Thomas Jahns 提到：
> Hi Alex,
>
> On 06/28/15 16:21, Alex Vong wrote:
> > Besides, the code base is quite old and as we know compilers always
> > add new warnings. I have asked upstream about fixing the warnings, but
> > it seems there is no easy way to fix all of them.
Hi Alex,
On 06/28/15 16:21, Alex Vong wrote:
Besides, the code base is quite old and as we know compilers always
add new warnings. I have asked upstream about fixing the warnings, but
it seems there is no easy way to fix all of them. So I want to know is
there a portable way to silent all compil
