This repository has been archived by the owner on Oct 4, 2023. It is now read-only.
build_and_run.sh is failing on 10.3 #98
Comments
|
The problem seems to be this line in .bazelrc: build --xcode_version=10.2.1 This basically tells bazel to require that version of Xcode, and refuse to build if it's not available. build_and_run.sh invokes bazel in that directory and gets that option applied. You can just remove that line from the .bazelrc. |
camillol
added a commit
to camillol/tulsi
that referenced
this issue
Aug 19, 2019
This fixes issue bazelbuild#98, where Tulsi fails to build with Xcode 10.3. When a specific Xcode version is specified on the command line (or in a .bazelrc), Bazel refuses to use any other version. The end-use installation instructions for Tulsi require building from source, using the build_and_run.sh script. This script is affected by the .bazelrc shipped with the source. As a result, whenever a new version of Xcode is released, Tulsi will automatically fail to build (unless the user kept an old version of Xcode around, which most won't). That is not a good default. If some tasks require a specific Xcode version to be specified (e.g. CI), it should be limited to those contexts, without limiting user's ability to build the project.
|
The xcode version lock has been removed on master |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
When following the setup instruction
errors out with
ERROR:
BUILD:12:1: in xcode_config rule @local_config_xcode//:host_xcodes: --xcode_version=10.2.1 specified, but '10.2.1' is not an available Xcode version. available versions: [10.3.0.10G8]. If you believe you have '10.2.1' installed, try running "bazel shutdown", and then re-run your command.
As 10.3 is about out for a month, how do I install tulsi? Any parameters I need to pass to the shell?
The text was updated successfully, but these errors were encountered: