RESOLVED FIXED322622
[CMake] WebKitLegacy should not link libPAL.a 
https://bugs.webkit.org/show_bug.cgi?id=322622
Summary [CMake] WebKitLegacy should not link libPAL.a
zak ridouh
Reported 2026-08-26 13:57:28 PDT
WebCore force-loads libPAL.a and re-exports it, so listing the static PAL target in WebKitLegacy_PRIVATE_LIBRARIES gave WebKitLegacy.framework a second copy of every PAL object it referenced thus duplicating PAL's state, not just its code, including soft-link class singletons and isoheap s_heapRef/s_heapSpec pairs. WebKitLegacy_FRAMEWORKS already lists PAL, which resolves to WebCore, and WebKit.framework relies on the same thing. Headers are unaffected: WebKitLegacy_PRIVATE_INCLUDE_DIRECTORIES lists PAL_FRAMEWORK_HEADERS_DIR. Xcode's WebKitLegacy.xcconfig never linked libPAL.a either. Matches Xcode behavior, and saves ~200KB of binary size.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2026-08-26 13:57:34 PDT
<rdar://problem/185923994>
zak ridouh
Comment 2 2026-08-26 13:59:44 PDT
Pull request: https://github.com/WebKit/WebKit/pull/72531
EWS
Comment 3 2026-09-01 07:31:08 PDT
Committed 320243@main (1d00164ce4f4): <https://commits.webkit.org/320243@main> Reviewed commits have been landed. Closing PR #72531 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.