How much diskspace and memory do I need, to compile Ungoogled Chromium?
I've got barely 4GB of RAM and usually something about 40GB of free space on my legacy Intel Core 2 Duo PC - and that's one of my reasons for choosing UC as a very light browser. Unfortunetely, while the browser itself works perfectly fine, the process of making it is extremely cumbersome if not impossible on older PCs.
Currently, I'm using ungoogled-chromium-appimage, but it's often even more delayed in its package development cycle, just like binaries on site and that's a bit worrying from security/patching standpoint.
Is there a way to compile Ungoogled Chromium on my config?
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks