[angle] Update to chromium/4472#18432
Conversation
c795ed0 to
045bad3
Compare
There was a problem hiding this comment.
Are those definitions only used when building or are they also needed by a consumer? (are the some header ifdefs pragmas)
There was a problem hiding this comment.
They do not appear to be exposed in any public headers. 👍
|
The x64_osx/x64_linux CI runs are failing on the |
|
@past-due That's related. Some files installed by angle are conflicts with opencl: Please remove them when installing angle. |
fbc6204 to
9ccd4c3
Compare
There was a problem hiding this comment.
I still wonder if this is correct or if the main target libEGL libGLESv2 libANGLE should use $<TARGET_OBJECTS:helper_targets> instead so that they don't need to get installed
There was a problem hiding this comment.
I'm afraid I have not had a chance to test this suggestion. As-is it is working fine for our purposes. @JackBoosY, your thoughts? (Otherwise, this is ready to go.)
9ccd4c3 to
7cd3987
Compare
|
Updated to pick up google/angle@d15be77 which was pushed to the |
|
Thanks @past-due! |
Update the
angleport (libANGLE) tochromium/4472(corresponding to the current Chromium Stable release).(This follows the recommendations in the libANGLE "Choosing an ANGLE branch" guide, matching the current Chromium Stable 91.0.4472.101.)
Which triplets are supported/not supported? Have you updated the CI baseline?
Same triplets as existing