[Webkit-unassigned] [Bug 46762] New: WebKit.gyp always builds as static_library, breaking shared chromium builds

[bugzilla-daemon at webkit.org]

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

           Summary: WebKit.gyp always builds as static_library, breaking
                    shared chromium builds
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mattm at chromium.org
                CC: fishd at chromium.org, dglazkov at chromium.org,
                    yaar at chromium.org


WebKit gets unconditionally built statically, regardless what the library setting of Chromium build is.  Since libwebkit is linked in multiple libraries in chrome, this causes issues with initializers and finalizers getting called multiple times.  Building webkit as a shared library fixes this issue.

I saw http://trac.webkit.org/changeset/50985 which changed it to be built statically under chromium and shared otherwise, and http://trac.webkit.org/changeset/53001 which caused it to always be built statically.   The reasoning isn't entirely clear to me, but it seems that, at least when building under chromium, we should just use the <(library) setting to build webkit.

Chromium bugs caused by this:
http://code.google.com/p/chromium/issues/detail?id=47575
http://code.google.com/p/chromium/issues/detail?id=47979

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.