-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
Can't generate Project on M1 #587
Comments
I do everything as described above, but I get a message
|
An Intel version of Bazel is no longer required, so the |
How can i generate a project on Mac M1? None of the instructions found for me can do this ( |
At which step are you getting stuck? |
Modify the values in variables.bzl - SKIP
Run:
but I get a message:
Run:
to solve this error I use but when executing the command:
get
|
An Intel version of Bazel is no longer required, so the --bazel_x86_64 argument was dropped. |
For anyone that has M1 Max, what I did is downloaded version 5 from here https://github.com/bazelbuild/bazel/releases/tag/5.0.0 and used that. Nothing else worked for me. |
UPD: this is solved: bazelbuild/bazel#12900 (comment)
Full list of steps for building TG:
curl -O -L https://github.com/bazelbuild/bazel/releases/download/4.0.0/bazel-4.0.0-darwin-x86_64
(or there'll be a newer version). I downloaded it to~/bazel-dist-4.0.0
mv bazel-4.0.0-darwin-x86_64 bazel
chmod +x bazel
git clone https://github.com/bazelbuild/bazel.git
or whatever). It should contain this commit bazelbuild/bazel@8c7e11agit apply ~/patches/ios_sim_arm64.patch
~/bazel-dist-4.0.0/bazel build --cpu=darwin_arm64 //src:bazel
Your build will be in
bazel-bin/src/bazel
. Copy it where you need it and runchmod +x bazel
Note that this build's version will be
no_version
:So you'll need to use flag
--overrideBazelVersion
. Also, Xcode version changed too already, so the full command for me was:Also note that
--bazel
uses new arm version, but--bazel_x86_64
is still that old x86 v3.7.0And this time simulator can be run!
Originally posted by @mahenzon in #467 (comment)
The text was updated successfully, but these errors were encountered: