[Webkit-unassigned] [Bug 177180] New: [CMake] Add ENABLE_WEB_CRYPTO option and make ENABLE_SUBTLE_CRYPTO depend on it.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 19 12:03:47 PDT 2017


https://bugs.webkit.org/show_bug.cgi?id=177180

            Bug ID: 177180
           Summary: [CMake] Add ENABLE_WEB_CRYPTO option and make
                    ENABLE_SUBTLE_CRYPTO depend on it.
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit WPE
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: bugs-noreply at webkitgtk.org

On r220445 <https://trac.webkit.org/r172758> the GTK port introduced the public configure option ENABLE_WEB_CRYPTO.

The idea is that users pass ENABLE_WEB_CRYPTO instead of ENABLE_SUBTLE_CRYPTO (subtle crypto is a terrible name)

I think we should use this naming also on the WPE port to enable SUBTLE crypto.

As someone that works on build recipes (Yocto) for WPE and GTK+, I will appreciate to have as much as possible identical config flags for the same features between both ports, to make easier code-sharing of recipe configs


So, if both GTK and WPE are going to use this naming then it make sense to mave also the definition to general CMake config like we do with other options

-- 
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/20170919/d9df439f/attachment-0001.html>


More information about the webkit-unassigned mailing list