Browse Source

Update bootstrap.sh

It now pulls in blaze.

We don't yet tell anyone to use blaze because we're still importing BUILD files, and
the one we have doesn't work. It appears to be for an older version.

./util/blaze //sys/src/libmach

2016/06/09 21:18:00 /home/rminnich/projects/harvey/harvey:6: While parsing cl were expecting [Func String LeftBrac EOF] but got Comma.
	in="elf64-x86-64",
 >^^^ < < <
2016/06/09 21:18:00 we couldn't find target //:sys/src/libmach

Our plan is to fix this one BUILD file so we can bootstrap others.

Here's the bigger question from Dan Cross: should we just be using Bazel?

Signed-off-by: Ronald G. Minnich <rminnich@gmail.com>
Author:    Sevki <s@sevki.org>
Sevki 3 years ago
parent
commit
ce7ad513ad
2 changed files with 6 additions and 0 deletions
  1. 1 0
      .gitignore
  2. 5 0
      bootstrap.sh

+ 1 - 0
.gitignore

@@ -64,3 +64,4 @@ usr/harvey/tmp
 build_out
 
 cron/lock
+/util/blaze

+ 5 - 0
bootstrap.sh

@@ -6,6 +6,10 @@ echo Building the build tool...
 GOBIN="$(pwd)/util" GOPATH="$(pwd)/util/third_party:$(pwd)/util" go get -d harvey/cmd/... # should really vendor these bits
 GOBIN="$(pwd)/util" GOPATH="$(pwd)/util/third_party:$(pwd)/util" go install github.com/rminnich/ninep/srv/examples/ufs harvey/cmd/...
 
+echo Downloading the blaze tool...
+curl -L http://sevki.co/get-build -o util/blaze
+chmod +x util/blaze
+
 # this will make booting a VM easier
 mkdir -p tmp
 
@@ -15,6 +19,7 @@ export ARCH=amd64
 # And build:
 ./util/build
 # See \`build -h' for more information on the build tool.
+
 To enable access to files, create a harvey and none user:
 sudo useradd harvey
 sudo useradd none