Re: variables defined in the makefile are ...

2016-01-03 Thread 積丹尼 Dan Jacobson
> "PS" == Paul Smith writes: PS> The right way to do this, as with any other variable you want to assign PS> to itself (PATH is not special), is to use simply-expanded variables PS> (:=) PS> PATH := $(PATH):../v4 Ah so on (info "(make) Appending") Using '+=' is similar to: objec

Re: variables defined in the makefile are ...

2016-01-03 Thread Paul Smith
On Mon, 2016-01-04 at 08:07 +0800, 積丹尼 Dan Jacobson wrote: > PATH=$$PATH:../v4 > PATH=$(PATH):../v4 > PATH=/home/jidanni/bin:/usr/bin:/bin:../v4 > PATH+=:../v4 > > Is to use the third version, > as the first will cause "ATH", > the second a recursive error, > and the fourth a blank in PATH that wi

variables defined in the makefile are ...

2016-01-03 Thread 積丹尼 Dan Jacobson
(info "(make) Environment") says When 'make' runs a recipe, variables defined in the makefile are placed into the environment of each shell. Not true. KK = 22 p: env|grep -c KK gives 0! This allows you to pass values to sub-'make' invoc