Skip to content

Add arm64x/ec builds - #398

Merged
Saancreed merged 3 commits into
jp7677:masterfrom
justradical:arm64ec-64bit
Sep 28, 2026
Merged

Saancreed merged 3 commits into
jp7677:masterfrom
justradical:arm64ec-64bit

Conversation

@justradical

@justradical justradical commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Adds a cross file, changes how 64 bit is detected by meson and adds arm64ec builds to some of the CI jobs.

The build-test-package-linux.yml can be modified to work with this, but it needs the toolchain from either the AUR or somewhere else so i dropped it.

build-llvm.yml does not work. xwin does not have arm64ec support so it fails to link:
lld-link: could not open 'softintrin.lib'

I want to try to get dxvk-nvapi into Proton arm64ec, to do that i need to get it into dxvk-nvapi here. That's the justification behind this change.

I built and tested this locally with Proton Experimental on a Retroid Pocket 6. It looks to be working as expected

@Saancreed Saancreed left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, Looks reasonable at a glance, but I have a few questions and/or suggestions.

Comment thread .github/workflows/build-proton.yml Resolved
Comment thread .github/workflows/build-proton.yml Resolved
Comment thread build-arm64x.txt Resolved
@justradical justradical changed the title Add arm64ec builds Add arm64x/ec builds Sep 26, 2026
@justradical

justradical commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor Author

I just added it everywhere i could now, please let me know if there's something here that you dont like/that i should revert again.

build-proton now builds on 1 runner as x86_64 with the cross toolchain.
build-test-package-linux also has the toolchain and builds arm64x so that we get them in artifacts. I'm testing the builds on my master branch and will make sure the artifact works.
package-release.sh now has a --build-arm64x flag that im using for these 2 workflows

One note here is that I'm not testing with an NVIDIA GPU and I dont have a good enough overview of nvapi to test everything

@justradical

Copy link
Copy Markdown
Contributor Author

@Saancreed Saancreed left a comment •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

One more minor request from me would be mentioning --build-arm64x as a valid optional flag for package-release.sh in our README. Other than that, I'll defer final judgement to Jens.

@justradical

Copy link
Copy Markdown
Contributor Author

👍

One more minor request from me would be mentioning --build-arm64x as a valid optional flag for package-release.sh in our README. Other than that, I'll defer final judgement to Jens.

done!

@Saancreed
Saancreed requested a review from jp7677 September 27, 2026 10:50

@jp7677 jp7677 left a comment •

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of annoying that we need to fetch the toolchain directly from github, but seems that this is unfortunately the way to go. See some very minor nits/suggestions, otherwise looks good and fine to get this in.

For the long term we could tweak the readme to mention arm64x there as well, but that is for another day. Same for exploring if we can go all the way meson (instead of msbuild directly) for msvc builds.

Comment thread .github/workflows/build-proton.yml Resolved

@jp7677 jp7677 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thanks! Do you mind squashing some commits before we merge this?

@justradical

Copy link
Copy Markdown
Contributor Author

Looks good. Thanks! Do you mind squashing some commits before we merge this?

yeah sure i can move some stuff around here

@justradical

Copy link
Copy Markdown
Contributor Author

I think this should be pretty good, i created a backup branch just in case

@Saancreed
Saancreed merged commit 0f26995 into jp7677:master Sep 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants