aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java
diff options
context:
space:
mode:
authorGravatar Lukacs Berki <lberki@google.com>2015-10-12 13:24:44 +0000
committerGravatar Lukacs Berki <lberki@google.com>2015-10-12 13:30:41 +0000
commit0d5d522bf9fc2ae42ab71ca60094c79eb988501c (patch)
tree41ea2e0937f4693870737f61ef8fefde8fdc9d5e /src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java
parentfc911c6af0a51cc1ab4b14be39f281ac1c86fb4a (diff)
Make the bootstrapping process work again after moving tools to the @bazel_tools repository.
The fix is to always compile tools when the Bazel binary is compiled and add the bootstrap arguments to bootstrap_test. This stil litters the git client with output files in random places, which is a bit difficult to fix, since //src:bazel expects these files to be there so that it can embed them into the output binary. I didn't notice this issue because tools/jdk/*_deploy.jar is in the .gitignore file, thus, when "git status" reported nothing, I asumed I ran the build in a clean client. -- MOS_MIGRATED_REVID=105206124
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/buildtool/BuildResultPrinter.java')
0 files changed, 0 insertions, 0 deletions