Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Flatpak aarch64 neo #16

Draft
wants to merge 7 commits into
base: master
Choose a base branch
from
Draft

Flatpak aarch64 neo #16

wants to merge 7 commits into from

Conversation

tytan652
Copy link
Owner

No description provided.

@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 12 times, most recently from 9f2e0af to fb793e8 Compare August 30, 2023 10:16
@tytan652 tytan652 added the Flatpak aarch64 Build Flaptak for the aarch64 architecture label Aug 30, 2023
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from fb793e8 to c401106 Compare August 30, 2023 10:20
@tytan652 tytan652 added Flatpak aarch64 Build Flaptak for the aarch64 architecture and removed Flatpak aarch64 Build Flaptak for the aarch64 architecture labels Aug 30, 2023
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 3 times, most recently from f081c07 to 1da465a Compare August 30, 2023 10:35
@tytan652 tytan652 removed the Flatpak aarch64 Build Flaptak for the aarch64 architecture label Aug 30, 2023
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 7 times, most recently from ade154b to ccbac57 Compare August 31, 2023 07:36
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 3 times, most recently from 3cd91e7 to 380a0e3 Compare September 9, 2023 19:24
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from 380a0e3 to a6cf209 Compare September 9, 2023 19:54
@tytan652 tytan652 added the Flatpak QEMU Allow Flatpak CI to use QEMU label Oct 9, 2023
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from a6cf209 to 7574e33 Compare October 9, 2023 09:30
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from 7574e33 to d0c6b7b Compare October 17, 2023 10:45
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 3 times, most recently from 7244986 to 2ce6361 Compare November 10, 2023 19:36
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 3 times, most recently from 03bfa10 to b764a6b Compare December 9, 2023 19:12
@tytan652 tytan652 mentioned this pull request Dec 9, 2023
Draft
6 tasks
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from b764a6b to d8c7fb0 Compare December 11, 2023 14:07
@tytan652 tytan652 added Flatpak QEMU Allow Flatpak CI to use QEMU and removed Flatpak QEMU Allow Flatpak CI to use QEMU labels Dec 11, 2023
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch 4 times, most recently from b8377ed to a9ef18c Compare December 12, 2023 07:51
@tytan652
plugins: Change obs-qsv11 enablement to reject unsupported architecture
d32f1be
@tytan652
build-aux: Disable QSV on non-x86_64 architecture
ca628b9 
None of Intel runtime supports non-x86_64 arches
@tytan652
build-aux: Add aarch64 support to Flatpak manifest
7086a35
@tytan652
CI: Move Flatpak workflow as reusable
3caa572 
Reusable workflow can have a matrix applied to the whole workflow
which cleanly workaround job with a matrix not having outputs per
iteration
@tytan652
CI: Split Flatpak in multiple jobs
50f7702 
This allows to workaround the 6 hours time limit per job. This is needed
to enable to build Flatpak with QEMU emulation.
@tytan652
CI: Add arch option to Flatpak build workflow
b22ef95
@tytan652
CI: Enable aarch64 Flatpak build
0a74df6 
Requires a label to be enabled on pull requests
@tytan652 tytan652 force-pushed the flatpak_aarch64_neo branch from a9ef18c to 0a74df6 Compare January 12, 2024 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Flatpak QEMU Allow Flatpak CI to use QEMU Seeking Testers
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tytan652