cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build: disable bazel-out symlink (#22375)

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

PR Close #22375
This commit is contained in:
Alex Eagle 2018-02-22 09:47:09 -08:00 committed by Victor Berchet
parent da1b4d5ea7
commit 17762390c9
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
tools/bazel.rc
View File

@ -14,12 +14,11 @@ test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test
# Filesystem interactions # # Filesystem interactions #
############################### ###############################
# Don't create bazel-* symlinks in the WORKSPACE directory. # Don't create symlinks like bazel-out in the project.
# These require .gitignore and may scare users. # These cause VSCode to traverse a massive tree, opening file handles and
# Also, it's a workaround for https://github.com/bazelbuild/rules_typescript/issues/12 # eventually a surprising failure with auto-discovery of the C++ toolchain in
# which affects the common case of having `tsconfig.json` in the WORKSPACE directory. # MacOS High Sierra.
# # See https://github.com/bazelbuild/bazel/issues/4603
# Instead, you should run `bazel info bazel-bin` to find out where the outputs went.
build --symlink_prefix=/ build --symlink_prefix=/
# Performance: avoid stat'ing input files # Performance: avoid stat'ing input files