Summary: | libWebCore.a: could not read symbols: Malformed archive while linking WebKitPluginProcess | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alban Browaeys <prahal> | ||||
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | cgarcia, dan, dbates, d.nomiyama, gustavo, kalevlember, mrobinson, plaes, rakuco | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
Alban Browaeys
2012-07-12 15:23:40 PDT
If we must continue splitting WebCore, I'm not sure having simply WebCoreA and a WebCoreB is a good way to split it. I'd rather see it split to match the organizational structure of the code. The s390x elf target in binutils got support for big archives recently as a reaction on https://bugzilla.redhat.com/show_bug.cgi?id=835957 (In reply to comment #1) > If we must continue splitting WebCore, I'm not sure having simply WebCoreA and a WebCoreB is a good way to split it. I'd rather see it split to match the organizational structure of the code. Based on the source structure, I would split 'WebCore/Modules' to libwebcoremodules. If this wouldn't be enough, then also: 'WebCore/dom' -> libwebcoredom 'WebCore/css' -> libwebcorecss 'WebCore/html' -> libwebcorehtml 'WebCore/svg' -> libwebcoresvg Any better ideas? libwebcoremodules is already split; I tried to split platform but it didn't work well with the pluginprocess. I think splitting svg could be a good idea, actually, maybe it'll not be as problematic, I'll give it a try. *** This bug has been marked as a duplicate of bug 102347 *** So, WebCore has been split - we now have libWebCore, libWebCoreModules, libWebCorePlatform and libWebCoreSVG, see: 134864 and 135538, thanks for the bug report! |