summaryrefslogtreecommitdiffhomepage
path: root/third_party/gvsync
diff options
context:
space:
mode:
authorAndrei Vagin <avagin@google.com>2019-05-03 14:11:55 -0700
committerShentubot <shentubot@google.com>2019-05-03 14:13:08 -0700
commit9e1c253fe814c85a316520bd6bd258adaa71df79 (patch)
tree688af9574f7d71aa144c1ba0c74b416542edbb0f /third_party/gvsync
parent24d8656585e6072ff7d5a00a7eb4bd25cba42dc4 (diff)
gvisor: run bazel in a docker container
bazel has a lot of dependencies and users don't want to install them just to build gvisor. These changes allows to run bazel in a docker container. A bazel cache is on the local file system (~/.cache/bazel), so incremental builds should be fast event after recreating a bazel container. Here is an example how to build runsc: make BAZEL_OPTIONS="build runsc:runsc" bazel Change-Id: I8c0a6d0c30e835892377fb6dd5f4af7a0052d12a PiperOrigin-RevId: 246570877
Diffstat (limited to 'third_party/gvsync')
0 files changed, 0 insertions, 0 deletions