-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
native bazel support for windows arm64 devices #14339
Comments
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Related: #14340 |
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Contains following changes to third_party: - Extended def_parser to handle ARM64 binaries - Add grpc patch to workaround build issues Fixes: bazelbuild#14339
Following changes are included - Fix AutoCpuConverter.java to identify win/arm64 CPU - Add win/arm64 JDK 17 - Add grpc patch to workaround build issues - Extend build_bazel_binaries.yml to cross-compile for win/arm64 - Fix msvc toolchain to look for tools in HostX86 directory as well Fixes: bazelbuild#14339
Thanks to @nsait-linaro, we now have native Windows ARM64 support #14340 |
@niyas-sait We want to upgrade Bazel's embedded JDK to JDK 20, but there seems to be no JDK 20 available for Windows Arm64 platform: https://github.com/adoptium/temurin20-binaries/releases/tag/jdk-20.0.1%2B9 Do you know when will it be available? |
Sorry I am not sure. I have moved to another role and haven't been keeping an eye on the latest status. The latest jdk seems to be 19 for the windows arm64 platform. |
Description of the problem / feature request:
Bazel native compilation support for windows on arm64 device is missing.
It is possible to do cross-compilation from windows x64 device but native compilation and toolchain are missing.
Feature requests: what underlying problem are you trying to solve with this feature?
Native Bazel support would simplify the build process and will be faster.
Native Bazel support is crucial for windows 10 as it doesn't have x64 emulation support.
What operating system are you running Bazel on?
Windows 10
What's the output of
bazel info release
?release 6.0.0-pre.20211110.1
What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
?https://github.com/bazelbuild/bazel.git
3a0bb4f6905a5f5426c477c03a453dc594f084ff
7894bfbfea9680d38439add1d45b9d6c3a129606
The text was updated successfully, but these errors were encountered: