Enable all arches - Githubissues

flathub / com.obsproject.Studio

This repository is no longer used to build OBS. Issues should be reported at https://github.com/obsproject/obs-studio

https://github.com/obsproject/obs-studio

29 stars 21 forks source link

Enable all arches #133

Open GeorgesStavracas opened 3 years ago

GeorgesStavracas commented 3 years ago

Remove the special-casing of x86_64 and i386, which should enable all arches to be used.

flathubbot commented 3 years ago

Started test build 48418

hfiguiere commented 3 years ago

Last time I tried, it was on a previous version, it crashed on startup on my Raspberry Pi. Because GL.

flathubbot commented 3 years ago

Build 48418 failed

hfiguiere commented 3 years ago

with the CEF binary, it's gonna be tough.

vchernin commented 2 years ago

I tried playing with building CEF with current master for aarch64, and I got nowhere useful. I think I'll open an issue at https://github.com/obsproject/obs-browser instead of spending more time fixing something I hardly understand to begin with.

tytan652 commented 2 years ago

I tried playing with building CEF with current master for aarch64, and I got nowhere useful. I think I'll open an issue at https://github.com/obsproject/obs-browser instead of spending more time fixing something I hardly understand to begin with.

OBS Studio doesn't support the latest CEF Look at this discussion on obs-studio https://github.com/obsproject/obs-studio/discussions/3853

I did build OBS Studio on aarch64 with CEF with my AUR packages obs-studio-tytan652 and cef-minimal-obs-bin.

I even made a try building a aarch64 flatpak with flatpak-builder github action master branch, but the missing piece is a stripped version or the CEF tarball to make it lighter, but it should work

hfiguiere commented 2 years ago

but the missing piece is a stripped version or the CEF tarball to make it lighter, but it should work

You can strip it in the flaptak build process.

tytan652 commented 2 years ago

but the missing piece is a stripped version or the CEF tarball to make it lighter, but it should work

You can strip it in the flaptak build process.

Yes, we could but:

273 MB VS 80 MB for the tarball
1.2 GB VS 238,8 MB once uncompressed

I prefer downloading the already stripped for caching deps in github actions. The github cache does not have an unlimited size.

hfiguiere commented 2 years ago

I don't think this is a problem on flathub.