tree 89601870b0e9f9a2ea147ecb53b8ff7110ed3574
parent ac6d4fd194c2d9aba13ce613ec373f627210b18d
author Keith Smiley <keithbsmiley@gmail.com> 1551307832 -0800
committer Copybara-Service <copybara-worker@google.com> 1551307936 -0800

Make Xcode setup more resilient

Previously if you tried to build a project from a entirely clean bazel
state, and ctrl-c'd while bazel was fetching the local_config_xcode
information, you would end up in a state where the
local_config_xcode/BUILD file contained error information, which made
the Apple crosstool unusable until you did a `clean --expunge`. Now the
Xcode setup calls `fail()` in those cases, which makes bazel re-run it
again the next time you try to build.

It is still possible to reproduce if you ctrl-c while the `xcodebuild
-version` command that determines if you have Xcode installed at all
runs. Because we want to support users who don't have Xcode installed on
macOS, we cannot fail in that case.

Fixes https://github.com/bazelbuild/bazel/issues/6056

Closes #7519.

PiperOrigin-RevId: 235997257