From f194d003662233bab694570d764c1e764753f4f6 Mon Sep 17 00:00:00 2001
From: Alex Eagle <alexeagle@google.com>
Date: Thu, 22 Feb 2018 09:47:09 -0800
Subject: [PATCH] build: disable bazel-out symlink (#22375)

It causes headaches on MacOS High Sierra, see https://github.com/bazelbuild/bazel/issues/4603

PR Close #22375
---
 tools/bazel.rc | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/tools/bazel.rc b/tools/bazel.rc
index 3069d9c4c6..800920282e 100644
--- a/tools/bazel.rc
+++ b/tools/bazel.rc
@@ -14,9 +14,12 @@ test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test
 # Filesystem interactions     #
 ###############################
 
-# Put bazel's symlinks under dist, so results go to dist/bin
-# There is still a `bazel-out` symlink created in the project root.
-build --symlink_prefix=dist/
+# Don't create symlinks like bazel-out in the project.
+# These cause VSCode to traverse a massive tree, opening file handles and
+# eventually a surprising failure with auto-discovery of the C++ toolchain in
+# MacOS High Sierra.
+# See https://github.com/bazelbuild/bazel/issues/4603
+build --symlink_prefix=/
 
 # Performance: avoid stat'ing input files
 build --watchfs