> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
Paul> Without GPATH, new files checked out will be placed in the target
Paul> directory; with it they will be updated in the source directory.
We could add that, but we couldn't rely on it.
Well, maybe we could, since really we only suppor
%% Ben Elliston <[EMAIL PROTECTED]> writes:
>> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
Paul> If you need to have the files created in their VPATH-found location
Paul> instead of in the local directly, use the GPATH variable to specify
Paul> which directories contain those
> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
Paul> If you need to have the files created in their VPATH-found location
Paul> instead of in the local directly, use the GPATH variable to specify
Paul> which directories contain those types of files.
Paul> See the GNU make manual
If you need to have the files created in their VPATH-found location
instead of in the local directly, use the GPATH variable to specify
which directories contain those types of files.
See the GNU make manual, and let me know.
I don't think this is the right behavior to make the default, though:
<[EMAIL PROTECTED]cc:
om> Subject: Misleading RCS behaviour
I have discovered some misleading behaviour in GNU Make. It pertains
to the combination of RCS files and VPATH. Here is a Makefile that I
have written to demonstrate the problem. Suppose this is a Makefile
generated by `configure' -- ie. it resides in the "build tree" (see
diagram below).