Arch Linux User Repository

@dlazar, happy to help! When you use yay and there's been an update to the Ladybird sources, it'll clone and build the whole thing all over again. Foregoing the convenience of yay and using makepkg directly will keep the same source tree clone intact. Therefore, your old CPUs will only have to compile the parts of it that have changed.

@sixtyfive

That is all I meant by macro! The short list of commands to run to use ladybird, but also keep it up to date. Of course, seeing the makepkg command means this will be a laborious task for the old CPUs, but that is fine! Thanks for the info.

@dlazar Dave, I don't know what you mean by "macro". For something like Ladybird, at its current stage of development, I would just not use yay at all. I'd clone this AUR repository and run makepkg myself whenever I wanted to update:

git clone https://aur.archlinux.org/ladybird-git.git
cd ladybird-git
makepkg -i

You'll have the Ladybird git repository available directly that way. No cache directory hidden away somewhere.

@sixtyfive, what would you recommend as a "try this macro" way of going about experimenting with ladybird browser then, at this stage of its existence? While you point to an alternative to yay -S ladybird-git I am not sure I follow what a superior method might be? Could you kindly paste one here for me to learn from?

@dlazar you might want to not use AUR helpers like yay for big source packages like this.

I am at a bit of a loss here, but as this project develops, is it standard that now that I have successfully compiled the AUR version of this, resulting in a working binary on my machine, that I now do a git pull, when desired, and re-compile from scratch, thus smoking my machine for as long as it takes? I believe at some point it'll be a routine binary to download, but for now, it's all or nothing in recompiling from scratch, right?

vcpkg is now in the repositories.

Can you maybe just use that package, instead of cloning it's sources (again)?

Regards!

I started a build fresh and from scratch and this time it completed without errors, so it appears pulling fresh code from git worked to smooth over the inconsistencies. Browser is working. Thanks!

@CxByte

I got a little further, but it choked and died in my overnight build as I awoke to this.

Downloading https://github.com/google/skia/archive/501e9efaa2fc929ec67c44da6dbaf9335264b559.tar.gz -> google-skia-501e9efaa2fc929ec67c44da6dbaf9335264b559.tar.gz
google-skia-501e9efaa2fc929ec67c44da6dbaf9335264b559.tar.gz.173832.part: error: download from https://github.com/google/skia/archive/501e9efaa2fc929ec67c44da6dbaf9335264b559.tar.gz had an unexpected hash
note: Expected: 978af9894d23d7b97d95d402bbf6c0c1401d63990361aae80166b620b0aa06d9dc2c75537850ff4c2df539735b4a12713cb29840613a15cbbff68590c48c4fac
note: Actual  : ec582c29b4cfe1052b6f09c23d68bd229c50658494672dc824c30c17fe617f60da1b935f09e366737cc1306671f4d34917c975259ed5f56fdbc7b719b2449db7
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:136 (message):
  Download failed, halting portfile.
Call Stack (most recent call first):
  scripts/cmake/vcpkg_from_github.cmake:120 (vcpkg_download_distfile)
  /home/yogi/.cache/yay/ladybird-git/src/ladybird/Meta/CMake/vcpkg/overlay-ports/skia/portfile.cmake:3 (vcpkg_from_github)
  scripts/ports.cmake:206 (include)


error: building skia:x64-linux failed with: BUILD_FAILED
See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
Elapsed time to handle skia:x64-linux: 10 min
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+skia
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[skia]+Build+error+on+x64-linux&body=Copy%20issue%20body%20from%20%2Fhome%2Fyogi%2F.cache%2Fyay%2Fladybird-git%2Fsrc%2Fbuild%2Fvcpkg_installed%2Fvcpkg%2Fissue_body.md

Completed submission of vcpkg-tool-gn:x64-linux@2025-01-27 to 1 binary cache(s) in 418 ms
Completed submission of vcpkg-gn:x64-linux@2024-02-22 to 1 binary cache(s) in 7.7 ms
-- Running vcpkg install - failed
CMake Error at /home/yogi/.cache/yay/ladybird-git/src/vcpkg/scripts/buildsystems/vcpkg.cmake:938 (message):
  vcpkg install failed.  See logs for more information:
  /home/yogi/.cache/yay/ladybird-git/src/build/vcpkg-manifest-install.log
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeDetermineSystem.cmake:146 (include)
  CMakeLists.txt:30 (project)


CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: ladybird-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
ladybird-git - exit status 4

xiota,dlazar: the 'default' preset was renamed in a recent commit (https://github.com/LadybirdBrowser/ladybird/commit/f2a10bda3274de751c23891dcd81df876dd734fe) that I missed. current version should build fine.

re using system packages instead of vcpkg, it should be possible and is technically on my todo list, but incremental builds are reasonably fast (unless the baseline gets bumped upstream, which usually forces a rebuild of most packages).