[Webkit-unassigned] [Bug 184379] New: Decide how to handle libWPEWebInspectorResources.so

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 6 18:17:07 PDT 2018


            Bug ID: 184379
           Summary: Decide how to handle libWPEWebInspectorResources.so
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit WPE
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at igalia.com
                CC: bugs-noreply at webkitgtk.org
            Blocks: 178894

libWPEWebInspectorResources.so is installed into libdir, which is probably OK, but:

 * It's not referenced in any pkg-config file, so it would be inappropriate for applications to link to it directly
 * The only use inside WebKit is in RemoteInspectorUtils.cpp, where it is dlopened

If it's only ever dlopened, it should probably go into pkglibdir instead, to get it out of the linker search path. But this makes me question how the web inspector is intended to work by default. How can it work if it's not linked to its resources? Is only remote inspector supported? Why is this so different from WebKitGTK+?

One way or another, we need to ensure it is API-versioned, so if we do not move it to pkglibdir, we should append the API version to the library name.

Referenced Bugs:

[Bug 178894] [WPE] Create the first stable release of WPE
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/20180407/ba812549/attachment-0002.html>

More information about the webkit-unassigned mailing list