Skip to content
This repository was archived by the owner on Jan 6, 2023. It is now read-only.

Upgrade to Chromium 62#376

Merged
zcbenz merged 49 commits intomasterfrom
upgrade-to-chromium-62
Feb 26, 2018
Merged

Upgrade to Chromium 62#376
zcbenz merged 49 commits intomasterfrom
upgrade-to-chromium-62

Conversation

@alexeykuzmin
Copy link
Copy Markdown
Contributor

@alexeykuzmin alexeykuzmin commented Oct 23, 2017

@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-61 branch from 856be70 to 453b17e Compare November 1, 2017 22:08
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from 70047d0 to e231a77 Compare November 2, 2017 02:59
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-61 branch 2 times, most recently from 42a88e0 to 46b7d69 Compare November 12, 2017 19:43
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch 4 times, most recently from 5a3168e to d466b16 Compare November 14, 2017 17:14
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-61 branch from f1958c9 to 23739c2 Compare November 17, 2017 10:42
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from f8d80db to fe30b3f Compare November 18, 2017 17:04
@zcbenz zcbenz force-pushed the upgrade-to-chromium-61 branch from 23739c2 to 5d55b4e Compare November 21, 2017 14:20
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from ac3f3dd to 8f525de Compare November 22, 2017 12:38
@alexeykuzmin alexeykuzmin changed the base branch from upgrade-to-chromium-61 to master November 24, 2017 09:24
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch 3 times, most recently from 423732e to 5fe3812 Compare December 8, 2017 08:23
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from 5fe3812 to 5d784eb Compare December 15, 2017 09:47
@codebytere codebytere requested review from tonyganch and removed request for tonyganch December 17, 2017 23:18
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch 2 times, most recently from 1d5f62f to 86a8670 Compare January 4, 2018 21:51
@zcbenz
Copy link
Copy Markdown
Contributor

zcbenz commented Jan 30, 2018

I'm rebasing this branch on master.

@zcbenz zcbenz force-pushed the upgrade-to-chromium-62 branch 4 times, most recently from 16ee275 to 5964d8f Compare January 31, 2018 02:50
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from 5964d8f to dfa5994 Compare February 21, 2018 09:47
@alexeykuzmin alexeykuzmin changed the title [WIP] Upgrade to Chromium 62 Upgrade to Chromium 62 Feb 21, 2018
alexeykuzmin and others added 23 commits February 21, 2018 20:54
The path to built libyuv lib has changed after the
"win: Rename clang_x64 to win_clang_x64 in build/toolchain/win"
has landed. See https://crbug.com/748501.
These changes are just backported from the newer Chromium revision.
Some of the patches (maybe even all) should be removed during
the next Chromium upgrade.

List of backported commits:

97f5f9df6988 Switch to Debian Stretch sysroot
1ed08ea9dbb0 Remove duplicated code in sysroot-creator.sh
99b48b47f11f Roll sysroots to include dbus changes
81e7f1791035 Unversion libdbus symbols in Linux sysroot
4dfcf263240a CrOs sysroot: update to Debian stretch and add libva* packages
140d82d6f8e2 Use xz level 9 compression for sysroots
b4ac34edef3a Make linux sysroot script print nothing in the happy case where it needs to do nothing.
95ecb913508e Add dconf to the sysroot
a1d30dcfbaa3 MIPS64: Add support for Stretch to sysroot scripts
Original commit:

commit 8a62aea7a676b02ef09717aabd7b4213420893fc
Author: Dominic Mazzoni <dmazzoni@chromium.org>
Date:   Fri Sep 1 22:03:03 2017 +0000

    Fix win clang build
Update clang to fix https://bugs.llvm.org/show_bug.cgi?id=34159
Original commit:

commit 01f121e242233f5fbbe2669d5d10df6fc0682949
Author: Hans Wennborg <hans@chromium.org>
Date:   Fri Sep 8 16:45:43 2017 +0000

    Roll Clang 310694-2:312679

    And remove the local patch
It seems like sysroot is expected to have it but it doesn't.
We should probably upstream this change or update the sysroot.
We've got a new sysroot from the upstream, but not the code fixes.
This patch should be removed after the upgrade to Chromium 63 or 64.
Node.js was updated in the master, we have to remove
V8's patches added during that update.
Those patches are either not needed for the Node.js 9.2.1,
or were already added in the Ch62 upgrade branch.
This is needed for service worker scripts, whose behavior was changed with
script streaming https://chromium-review.googlesource.com/c/chromium/src/+/597033
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from dfa5994 to 5cb70dc Compare February 22, 2018 09:23
@alexeykuzmin alexeykuzmin force-pushed the upgrade-to-chromium-62 branch from 5cb70dc to 322eb12 Compare February 22, 2018 10:39
@zcbenz zcbenz merged commit c3e37d7 into master Feb 26, 2018
@alexeykuzmin alexeykuzmin deleted the upgrade-to-chromium-62 branch February 26, 2018 16:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants