[Webkit-unassigned] [Bug 200306] [GTK][WPE] Fix gtkdoc build with "build-webkit --32-bit" on 64-bit hosts

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jul 31 11:17:32 PDT 2019


--- Comment #9 from Loïc Yhuel <loic.yhuel at softathome.com> ---
(In reply to Michael Catanzaro from comment #7)
> (In reply to Loïc Yhuel from comment #4)
> > > (I'm also sure you know not to use build-webkit for production builds. ;)
> > Well, we still use build-webkit on our downstream target builds (but main
> > compiler flags come from a CMake toolchain file, since it's cross-compiled).
> > It behaves slightly better for development when there are changes, and
> > having two different ways to build WebKit could lead to differences between
> > what the developer sees, and what the integrator gets.
> Are you manually disabling flags like ENABLE_DEVELOPER_MODE=ON and
> ENABLE_EXPERIMENTAL_FEATURES=ON? Does build-webkit even work without the
> testing JHBuild environment? Regardless, I suppose it doesn't matter for
> this bug....
Yes, we disable those flags by default, and only turn them on when needed (our build-webkit command line is in fact quite long, and contains roughtly as many cmake arguments than script ones).

I rarely use JHBuild personally :
 - For our downstream builds, all needed WPE dependencies are built by our buildsystem before WebKit.
 - For upstream host builds, Fedora has enough devel packages for WPE (now even libwpe and wpebackend-fdo) or GTK. Obviously on Ubuntu 18.04 it's a lot more complex, many flags need to be manually disabled since the packages are too old, or even missing.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190731/e5d29ec4/attachment.html>

More information about the webkit-unassigned mailing list