You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Enable native support for Windows on arm64 (Part 1)
Contains following changes to third_party:
- Extended def_parser to handle ARM64 binaries
- Add grpc patch to workaround build issues
Closes: bazelbuild#14689
Partial commit for third_party/*, see bazelbuild#14689.
Signed-off-by: Yun Peng <[email protected]>
* Enable native support for Windows on arm64
This PR will enable cross-compilation of Bazel binaries for win/arm64 from win/x64
`bazel build -c opt --cpu=x64_arm64_windows //src:bazel.exe`
Generated bazel executable can be used for native compilation in win/arm64
`bazel.exe build //main:hello-world`
Following changes are included
- Add win/arm64 JDK 17
- Fix AutoCpuConverter.java to identify win/arm64 CPU
- Extend build_bazel_binaries.yml to cross-compile for win/arm64
- Fix msvc toolchain to look for tools in HostX86 directory as well
- add clang-cl support for windows/arm64 host
- Extend host_windows config to handle windows x64 and arm64 hosts.
Closesbazelbuild#14340.
PiperOrigin-RevId: 425919351
* [windows/arm64] Add missing JDK toolchain for java build
Extend configurations to add JDK 11 and 17 for windows/arm64 platforms.
This should fix the Java builds on windows/arm64
Closesbazelbuild#14700.
PiperOrigin-RevId: 427737536
* add missing openjdk11_windows_arm64_archive
* Deduplicate urls parsed to reduce crawl requests
bazelbuild#14700 added couple more URLs to fetch JDK package and seems to be causing some infrastructure as discussed in bazelbuild#14700.
This patch workaround the issue by removing the duplicated URLs and reduce the crawl request.
Closesbazelbuild#14763.
PiperOrigin-RevId: 427464876
* fix jdk_http_archives.tmpl
0 commit comments