Package Details: webkitgtk 3:2.4.11-28

Git Clone URL: https://aur.archlinux.org/webkitgtk.git (read-only, click to copy)
Package Base: webkitgtk
Description: Legacy Web content engine for GTK+ 3
Upstream URL: https://webkitgtk.org/
Licenses: custom
Conflicts: libwebkit3, webkitgtk3
Provides: libwebkit3, webkitgtk3
Replaces: libwebkit3, webkitgtk3
Submitter: City-busz
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 71
Popularity: 0.76
First Submitted: 2017-06-30 07:40 (UTC)
Last Updated: 2024-11-16 02:41 (UTC)

Sources (16)

Pinned Comments

frealgagu commented on 2019-04-14 18:13 (UTC) (edited on 2020-12-06 03:31 (UTC) by frealgagu)

FAQ

Q: What's the difference between this package and extra/webkit2gtk?

A: webkitgtk/webkitgtk2 provides WebKit1 API/ABI, which is not compatible with WebKit2 API/ABI provided by extra/webkit2gtk. WebKitGTK+ 2.4.x is the latest branch that provides WebKit1 API. Later branches provides WebKit2 API only.

Please don't flag it as out-of-date.


Q: Are there binaries for this package somewhere?

A: I maintain the latest built package at https://github.com/frealgagu/archlinux.webkitgtk/releases


Q: "error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory"

A: You'll need to rebuild against the latest version of ICU.


Q: "error: ‘WTF::StringImpl::StaticASCIILiteraicASCIILiteral’ has not been declared" or any enchant errors.

A: If you are building in parallel, try disabling parallel using -j1 in /etc/makepkg.conf


Q: Why building takes too long time?

A: WebKit is inherently big and complex. You can modify /etc/makepkg.conf or PKGBUILD directly to build it in parallel.

  • Change "make all stamp-po" by "make -j x all stamp-po" in PKGBUILD replacing x by cores your machine has. (Thanks to @MadMe)

  • Change /etc/makepkg.conf in that way: https://wiki.archlinux.org/index.php/makepkg#Parallel_compilation under # ARCHITECTURE, COMPILE FLAGS use MAKEFLAGS="-j9" # It should be one more than your virtual CPUs. (Thanks to @tuxsavvy).

However be pending if errors occur as mentioned in previous question.


Q: How much I want to wait to a successful compilation?

A: It varies of your PC's processor and RAM, the times shared in the comments are as follow:

  • 3.5 hours to build on core i5 laptop with 8G of RAM, makeflags j4. (@cabbage)

  • 13.5 hours to build on AMD Athlon X2, makeflags j1 (@Bonnietwin).

  • 5-6 hours on Core2Duo E8400 with 8GB RAM, makeflags j2 (tuxsavvy).

  • 50 minutes on 6c/12t 3.3GHz (@kubrick).

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 16 Next › Last »

bsulyok commented on 2018-08-16 21:47 (UTC)

I started building the pkg file, but as after about 4 hours it still did not finish I terminated the command, what could have gone wrong?

Scimmia commented on 2018-04-30 14:30 (UTC)

Because this isn't webbkit2

dalu commented on 2018-04-30 14:05 (UTC)

isn't this severely outdated and vulnerable? latest version of webkit2gtk+ is at the time of writing 2.20.1 (stable).

So why is this at version 2.4.11 and not flagged as being outdated?

yan12125 commented on 2018-04-30 05:41 (UTC)

@ReDemoNBR: Thanks and done :)

Scimmia commented on 2018-04-29 15:38 (UTC)

Or you should read the AUR wiki page and figure out how things actually work

dafta commented on 2018-04-29 15:35 (UTC)

The following build dependencies are missing: automake, bison, flex. You should probably add them to makedepends.

ReDemoNBR commented on 2018-04-23 05:11 (UTC)

I've been building the last versions of this package for my Raspberry Pi 3 (arch 'armv7h') correctly for some months already and I think it is time to report that it is safe to add 'armv7h' in arch. Same is valid for webkitgtk2 package :D

Takes around 40-50 hours to build it but, believe it or not, it does work.

But please let the version as it is, otherwise we will have have to update it again :)