From 17762390c9a3bc0c195f9864b0069b4b4112b1a9 Mon Sep 17 00:00:00 2001 From: Alex Eagle 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 | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/tools/bazel.rc b/tools/bazel.rc index c121e13682..800920282e 100644 --- a/tools/bazel.rc +++ b/tools/bazel.rc @@ -14,12 +14,11 @@ test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test # Filesystem interactions # ############################### -# Don't create bazel-* symlinks in the WORKSPACE directory. -# These require .gitignore and may scare users. -# Also, it's a workaround for https://github.com/bazelbuild/rules_typescript/issues/12 -# which affects the common case of having `tsconfig.json` in the WORKSPACE directory. -# -# Instead, you should run `bazel info bazel-bin` to find out where the outputs went. +# 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