Package Details: ladybird-git r69047.90d466e7e98-1

Git Clone URL: https://aur.archlinux.org/ladybird-git.git (read-only, click to copy)
Package Base: ladybird-git
Description: Truly independent web browser
Upstream URL: https://github.com/LadybirdBrowser/ladybird
Keywords: browser
Licenses: BSD-2-Clause
Conflicts: ladybird
Provides: ladybird
Submitter: xyproto
Maintainer: CxByte
Last Packager: CxByte
Votes: 22
Popularity: 3.51
First Submitted: 2022-09-12 14:59 (UTC)
Last Updated: 2025-05-12 19:30 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

RoblKyogre commented on 2024-07-13 08:43 (UTC)

Fyi this package seems to build fine on my system without having vcpkg installed, as it compiles and uses it as part of the build process. Could you consider either removing it from makedepends, or skip compiling it as a part of this build process? Feel free to keep it if it is actually necessary, tho.

seo.disparate commented on 2024-07-10 02:40 (UTC)

It looks like the 32x32 icon was removed and replaced by this commit https://github.com/LadybirdBrowser/ladybird/commit/fe551d3eff06adddc7d2aa60c3f62d67bebb7a4f , so the PKGBUILD will need to use the new icon path during package().

seo.disparate commented on 2024-07-10 02:21 (UTC)

It looks like nasm needs to be added to the makedepends array for it to build.

circl commented on 2024-07-02 15:05 (UTC)

@timschumi The build process seems to be stable for now

timschumi commented on 2024-06-04 16:26 (UTC)

Let's wait until the new build process has stabilized, last I heard was that there might still be some moving-around of certain parts.

atticf commented on 2024-06-03 10:11 (UTC)

This should build from the new fork: https://github.com/LadybirdWebBrowser/ladybird

https://awesomekling.substack.com/p/forking-ladybird-and-stepping-down-serenityos

timschumi commented on 2024-04-01 15:40 (UTC)

Cloning the repository is currently blocking on an upstream curl bug [1][2]. Once that is resolved I can look into why building the package currently fails.

[1] https://gitlab.archlinux.org/archlinux/packaging/packages/curl/-/issues/6 [2] https://github.com/curl/curl/issues/13229

LPW00 commented on 2024-04-01 01:06 (UTC)

Build fails with

{standard input}: Assembler messages: {standard input}:10: Error: file not found: /usr/src/debug/ladybird-git/serenity/Userland/Libraries/LibCompress/BrotliDictionary.cpp.dict.bin

I don't really know what I'm doing so I just copied the ladybird-git folder to /usr/src/debug/ and when I ran makepkg again, it built properly. I assume that could actually be fixed in the PKGBUILD though, so I thought I'd let you know.

Also, just downloading the snapshot, extracting it and running makepkg -sirc in the ladybird-git folder, the git clone operation failed with

error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400 fatal: expected 'packfile'

Idk why that happens, might be my fault somehow. When I clone the repo manually before running makepkg, it doesn't complain.

jamnor commented on 2023-11-03 03:21 (UTC)

This built fine for me, but I needed to change the /usr/share/applications/ladybird.desktop file for it to show up in GNOME. The executable I get is /usr/bin/Ladybird, not /usr/bin/ladybird.

So I had to change it from this:

Exec=ladybird

To this:

Exec=Ladybird

Then I updated my desktop entries database:

sudo update-desktop-database

And I can now find and launch Ladybird from GNOME.

Evergreen commented on 2023-06-28 15:41 (UTC)

As of package version r50376.5312a140fe-1, it appears that qt6-multimedia is now a dependency.

-- Could NOT find Qt6Multimedia (missing: Qt6Multimedia_DIR)
CMake Error at CMakeLists.txt:76 (find_package):
  Found package configuration file:

    /usr/lib/cmake/Qt6/Qt6Config.cmake

  but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be NOT
  FOUND.  Reason given by package:

  Failed to find required Qt component "Multimedia".

  Expected Config file at
  "/usr/lib/cmake/Qt6Multimedia/Qt6MultimediaConfig.cmake" does NOT exist



  Configuring with --debug-find-pkg=Qt6Multimedia might reveal details why
  the package was not found.

  Configuring with -DQT_DEBUG_FIND_PACKAGE=ON will print the values of some
  of the path variables that find_package uses to try and find the package.

« First ‹ Previous 1 2 3 4 5 Next › Last »