Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[6.4.0] Update unknown Xcode version error message and provide an environment variable to force re-evaluation #19540

Merged
merged 1 commit into from
Sep 15, 2023
Merged

[6.4.0] Update unknown Xcode version error message and provide an environment variable to force re-evaluation #19540

merged 1 commit into from
Sep 15, 2023

Commits on Sep 15, 2023

  1. Update unknown Xcode version error message and provide an environment… 

    … variable to force re-evaluation

As of c747ae7, you need to run `bazel sync --configure` instead of `bazel shutdown`, to force re-finding of Xcode versions.

Certain setups have a hard time running that new command, versus previously only having to cause Bazel to restart. To accommodate that, I’ve also added the `XCODE_VERSION` variable to `environ` (to match a similar use defined here: bazelbuild/apple_support@ddf25c2), which allows those setups to force the re-evaluation by using `--repo_env`. And since the `default` attribute is influenced by `DEVELOPER_DIR`, I've included that in `environ` as well.

Closes bazelbuild#19512.

PiperOrigin-RevId: 565610471
Change-Id: Ideca7165308ce53fdf1ce22b31eeb7a9e681dedc
    @brentleyjones @bazel-io
    brentleyjones authored and bazel-io committed Sep 15, 2023
    Configuration menu
    Copy the full SHA
    fc22e73 View commit details
    Browse the repository at this point in the history