aboutsummaryrefslogtreecommitdiffstats
path: root/build.ninja.in
diff options
context:
space:
mode:
authorDan Willemsen <dwillemsen@google.com>2015-07-14 00:39:06 -0700
committerDan Willemsen <dwillemsen@google.com>2015-09-17 23:42:25 -0700
commit87b17d1ff46ab86ab897c50435c423f28be4895f (patch)
tree69d5b2ed53c5b99aacef6b3d692256ec0b671d21 /build.ninja.in
parentc3ba6cb9707730e0fc553fa86b9fe6b6c9bbb4b9 (diff)
downloadbuild_soong-87b17d1ff46ab86ab897c50435c423f28be4895f.tar.gz
build_soong-87b17d1ff46ab86ab897c50435c423f28be4895f.tar.bz2
build_soong-87b17d1ff46ab86ab897c50435c423f28be4895f.zip
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
Diffstat (limited to 'build.ninja.in')
-rw-r--r--build.ninja.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/build.ninja.in b/build.ninja.in
index cf585f56..d46df703 100644
--- a/build.ninja.in
+++ b/build.ninja.in
@@ -32,7 +32,7 @@ g.bootstrap.srcDir = @@SrcDir@@
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