Apple Silicon Universal Binary Build
zinozzino opened this issue · 3 comments
I managed to also build the arm64 version for macos using LLVM 11.1.0-rc2 both on my build system and on GitHub Actions:
https://github.com/kramred/ungoogled-chromium-macos/releases/tag/88.0.4324.146-1.1_arm64
The arm64 build on GitHub Actions took 1d 4h 5m 33s
I think it is sufficient to provide both versions (x86-64 and arm64) individually, although they could probably also be merged as described in chromium docs. I assume that the universal binary would then be approximately double the size.
What would be the benefit of a universal binary instead of two architecture specific ones?
One possible thing is that I downloaded the arm64 Chrome from Google, and I see it is listed as a Universal binary in the Finder. When I test WidevineCDM, it works on that. It does not work on your arm64-only build. On that one, if I copy the mess over from Chrome, it fails to load. I noticed that in Contents/Frameworks/Chromium Framework.framework/Libraries/WidevineCdm/_platform_specific, there is only a mac_x64 folder. Hardly a huge issue, but it is possible that the framework only loads if you also have the x64 build as well as arm64. There could be other things that are, perhaps, not fully built for arm64. To be 100% sure, I'd have to build a "Googled" arm64-only version of Chromium to compare to, which I have not. This is just something I noticed using your build that could, in fact, be a reason to make such a large download.