Setting up an SDK/Pacman repo for ARM64 #4186
Replies: 2 comments 15 replies
-
I already added an But before we can populate that, we need to teach our branch-deploy-based automation to build those packages. To do that, we need to set up self-hosted runners (most likely using a separate workflow using your excellent Azure Resource Management template combined with the To address the slowness of The The biggest obstacle for the
Indeed, it should probably look somewhat like this: [git-for-windows-clang64]
Server = https://wingit.blob.core.windows.net/aarch64 |
Beta Was this translation helpful? Give feedback.
-
Here's a PR that teaches the pipeline to build
|
Beta Was this translation helpful? Give feedback.
-
Now that we can build pretty much all Git for Windows artifacts for ARM64, I'd like to suggest that we set up an ARM64 SDK and/or Pacman repo as a next step.
There's a few places that are currently a bit painful to maintain due to the lack of an SDK/Pacman repo:
setup-git-for-windows-sdk
GitHub Action is significantly slower on ARM64 because it needs to install a bunch ofclangarm64
dependencies every time it runs on ARM64. Caching might be a solution, but having a proper SDK would be even better.git-artifacts
CI pipeline needs to download the pre-built dependencies below as they would take a long time to build.We'll at least need the following packages in this SDK and/or Pacman repo:
Then the Pacman repo needs to be added to
/etc/pacman.conf
(like here).Curious to hear what's needed to set up all of this!
Beta Was this translation helpful? Give feedback.
All reactions