commit 87b17d1ff46ab86ab897c50435c423f28be4895f
author Dan Willemsen <dwillemsen@google.com> Tue Jul 14 00:39:06 2015 -0700
committer Dan Willemsen <dwillemsen@google.com> Thu Sep 17 23:42:25 2015 -0700
tree 69d5b2ed53c5b99aacef6b3d692256ec0b671d21
parent c3ba6cb9707730e0fc553fa86b9fe6b6c9bbb4b9

Use SRCDIR as a working directory

The existing behavior of using the build directory as the working
directory is useful if you want to move/copy the output directory around
and SRCDIR still refers the the source. But, it's more useful to have
the source directory be the working directory. Tools like cpp(__FILE__)
and other debug prints embed relative paths from the working directory.
We also have tools that expect the working directory to be $TOP.

Change-Id: Ia0f1d3c6b7df72d61cf5628efa2baa98bd19775b

build.ninja.in

diff --git a/build.ninja.in b/build.ninja.in
index cf585f5..d46df70 100644
--- a/build.ninja.in
+++ b/build.ninja.in
@@ -32,7 +32,7 @@
 builddir = ${g.bootstrap.buildDir}/.minibootstrap
 
 rule g.bootstrap.bootstrap
-    command = ${g.bootstrap.bootstrapCmd} -i ${in} -b ${g.bootstrap.buildDir}
+    command = BUILDDIR=${g.bootstrap.buildDir} ${g.bootstrap.bootstrapCmd} -i ${in}
     description = bootstrap ${in}
     generator = true