| 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.77 |
| First Submitted: | 2017-06-30 07:40 (UTC) |
| Last Updated: | 2024-11-16 02:41 (UTC) |
@slav I always maintain the lastest build in https://github.com/frealgagu/archlinux.webkitgtk/releases
For version 3:2.4.11-22 this is the direct url: https://github.com/frealgagu/archlinux.webkitgtk/releases/download/3_2.4.11-22/webkitgtk-3.2.4.11-22-x86_64.pkg.tar.zst
Can someone please provide compiled package webkitgtk-3:2.4.11-22 webkitgtk2-3:2.4.11-22 ? Thanks, Slav
Hi @frealgagu, I expect it builds in a chroot jail because gtk-doc is not installed in the jail and therefore autoconf is not trying to configure it. I'm not sure what effects that has on the generated package. I'll setup a jail when I get a chance and see what is different with and without gtk-doc installed.
Interestingly the whole reference manual looks to be in the src/webkitgtk-2.4.11/Documentation subdir in HTML format and it was built using gtk-doc by upstream. I guess this could be added to a -doc package.
@Scindix @Hubro @Baltazar72 @BruceR @u666sa Today I've compiled the package without make any changes. Have you tried to make in a chroot jail? Otherwise I don't know why that's happening.
I had the gtkdocsize error as well. But I can confirm that the patch @BruceR posted works. At least for me. Thanks for your service @BruceR.
@Baltazar72 Dude you are a lifesaver! I got it to build now and I'm back on the company VPN (with pulse-secure), what a massive pain the last week has been without it.
Adding this patch to configure.ac allowed me to build it with autoconf 2.70.
$ cat gtk-doc.patch
diff --git a/configure.ac b/configure.ac
index d0bb1a1..5eee551 100644
--- a/configure.ac
+++ b/configure.ac
@@ -36,6 +36,13 @@ AM_INIT_AUTOMAKE([foreign subdir-objects dist-xz no-dist-gzip tar-ustar])
AM_MAINTAINER_MODE([enable])
m4_include([Source/autotools/SetupAutomake.m4])
+# check for gtk-doc
+m4_ifdef([GTK_DOC_CHECK], [
+GTK_DOC_CHECK([1.14],[--flavour no-tmpl])
+],[
+AM_CONDITIONAL([ENABLE_GTK_DOC], false)
+])
+
######################################################################################
# Processing of configuration files
######################################################################################
See https://developer.gnome.org/gtk-doc-manual/stable/settingup_autoconf.html.en
Hi @Hubro . I downgraded autoconf from 2.70-1 to 2.69-7 to avoid the gtkdocize build error.
This package is failing to build for me:
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'Source/autotools'.
libtoolize: copying file 'Source/autotools/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'Source/autotools'.
libtoolize: copying file 'Source/autotools/libtool.m4'
libtoolize: copying file 'Source/autotools/ltoptions.m4'
libtoolize: copying file 'Source/autotools/ltsugar.m4'
libtoolize: copying file 'Source/autotools/ltversion.m4'
libtoolize: copying file 'Source/autotools/lt~obsolete.m4'
libtoolize: Remember to add 'LT_INIT' to configure.ac.
libtoolize: Consider adding '-I Source/autotools' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: configure.ac: not using Intltool
autoreconf: running: gtkdocize --copy
gtkdocize: GTK_DOC_CHECK not called in ./configure.ac
autoreconf: error: gtkdocize failed with exit status: 1
gtkdocize: GTK_DOC_CHECK not called in ./configure.ac autoreconf: error: gtkdocize failed with exit status: 1
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 FLAGSuseMAKEFLAGS="-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).