Re: variable value lost with "include" directive

[Aditya Kher]

> No, they're carried through.  You can verify this by adding this line
> to ../../bin/Makefile right after the VPATH appending:
>
> $(warning VPATH=${VPATH})

That was helpful.

> Is the '../include' directory relative to the directory in which you
> invoked gmake?  If not, that's your problem.  'include' does not
> change the base directory from which make interprets relative paths.

Yes. it was a gotcha. Thanks. But lets say, if

the bin/Makefile is going to be included from directories foo/Makefile
and boo_internal/Makefile:

some_dir
  |
  |
 +--bin/Makefile
  |
  |
 +--foo/Makefile
  |
  |
 +--boo/Makefile
  |      |
  |      +--boo_internal/Makefile
  |
 +---coo

Then is the only place to specify the VPATH is in
boo_internal/Makefile, boo/Makefile and NOT in bin/Makefile? Beacuse
as you correctly mentioned
"'include' does not  change the base directory from which make
interprets relative paths."

(frankly I would like to specify the VPATH in bin/Makefile since- the
paths are related to stuff that is processed in bin/Makefile. The
paths do not make sense in Makefiles that call the bin/Makefiles)

Ideas?
-aditya