Bug 237748 - Catalyst JavaScriptCore, WebCore, WebKitLegacy, and WebKit shouldn't be copied to the Secondary Path
Summary: Catalyst JavaScriptCore, WebCore, WebKitLegacy, and WebKit shouldn't be copie...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Michael Saboff
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-03-10 16:40 PST by Michael Saboff
Modified: 2022-03-10 17:21 PST (History)
13 users (show)

See Also:


Attachments
Patch (15.20 KB, patch)
2022-03-10 16:53 PST, Michael Saboff
mark.lam: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Saboff 2022-03-10 16:40:52 PST
I built a Mac Catalyst root and found that Mac Catalyst versions of JavaScriptCore, WebCore, WebKitLegacy, and WebKit were present in the secondary content path. These Catalyst frameworks shouldn’t be copied.
Comment 1 Michael Saboff 2022-03-10 16:40:58 PST
<rdar://90127039>
Comment 2 Michael Saboff 2022-03-10 16:53:02 PST
Created attachment 454429 [details]
Patch
Comment 3 EWS Watchlist 2022-03-10 16:54:50 PST
Note that there are important steps to take when updating ANGLE. See https://trac.webkit.org/wiki/UpdatingANGLE
Comment 4 Mark Lam 2022-03-10 16:57:26 PST
Comment on attachment 454429 [details]
Patch

rs=me
Comment 5 Mark Lam 2022-03-10 17:00:06 PST
Comment on attachment 454429 [details]
Patch

rs=me
Comment 6 Mark Lam 2022-03-10 17:01:06 PST
Comment on attachment 454429 [details]
Patch

rs=me
Comment 7 Michael Saboff 2022-03-10 17:21:00 PST
Committed r291139 (248299@trunk): <https://commits.webkit.org/248299@trunk>