Bug 207080

Summary: WebCore links to stale libANGLE.dylib instead of libANGLE.a
Product: WebKit Reporter: James Darpinian <jdarpinian>
Component: ANGLEAssignee: James Darpinian <jdarpinian>
Status: RESOLVED WONTFIX    
Severity: Normal CC: ap, dino, ews-watchlist, graouts, justin_fan, kbr, kondapallykalyan
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 198948, 205483, 206318    
Attachments:
Description Flags
Rename libANGLE.a to libANGLE-static.a dino: review-, dino: commit-queue-

Description James Darpinian 2020-01-31 16:29:09 PST 
Under some circumstances that I haven't pinned down yet, WebCore will load libANGLE.dylib instead of libANGLE-shared.dylib. libANGLE.dylib is no longer produced by the build, and old stale copies are just hanging around in people's build directories, including on the bots. This is the root cause of the bot test failures that keep causing our ANGLE updates patches to be rolled back.
Comment 1 James Darpinian 2020-02-03 16:14:50 PST 
Created attachment 389591 [details]
Rename libANGLE.a to libANGLE-static.a
Comment 2 EWS Watchlist 2020-02-03 16:15:30 PST 
Note that there are important steps to take when updating ANGLE. See http://trac.webkit.org/wiki/UpdatingANGLE
Comment 3 Kenneth Russell 2020-02-03 17:12:40 PST 
Great work James diagnosing this problem from the binaries from the build bots, and coming up with a future-proof fix!
Comment 4 Dean Jackson 2020-02-04 14:15:19 PST 
Comment on attachment 389591 [details]
Rename libANGLE.a to libANGLE-static.a

Unfortunately we can't do this, because the Apple build system will freak out that we're no longer producing a libANGLE.a, even if we update WebCore at the same time because everything is built in isolation. This is why the change to a dylib was eventually called libANGLE-shared.dylib - I learnt the hard way. 

The good news is that the bots with the stale file have been cleared, and if it happens again we know what to do.

We'll also move to libANGLE-shared.dylib soon.
Comment 5 James Darpinian 2020-02-04 14:33:40 PST 
OK, seems like the easiest thing to do is just wait for the shared library switch, and live with the possibility that some people's builds might be broken in the meantime.