[Webkit-unassigned] [Bug 172758] [GTK] Enable SUBTLE_CRYPTO in GTK+ releases

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 9 05:06:37 PDT 2017


--- Comment #24 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---

 * Debian Stable bot (on Jessie still): https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20Debian%20Stable%20%28Build%29
   - Installed libgcrypt 1.7 from the jessie backports repository.
 * Ubuntu LTS Bot (16.04): https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20Ubuntu%20LTS%20%28Build%29
   - Configured it to build with -DENABLE_WEB_CRYPTO=OFF via the environment variable  BUILD_WEBKIT_ARGS supported by the script build-webkit.

That way:

 * The default configuration of WebKitGTK+ remains build-able on Debian 8 (Jessie) (but you have to use a few packages from backports like clang-3.8 and newer libgcrypt)

 * The default configuration of WebKitGTK+ is not longer build-able on Ubuntu 16.04, but you can build without web crypto by simply passing -DENABLE_WEB_CRYPTO=OFF to CMake. This bot will test this to ensure no breakage happens with WEB_CRYPTO=OFF.

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/20170809/1ac5800d/attachment-0001.html>

More information about the webkit-unassigned mailing list