commit | 2221bd86207794327bd890681cb011f6e1b2a73e | [log] [tgz] |
---|---|---|
author | Adrian Taylor <adetaylor@chromium.org> | Fri Dec 03 18:04:48 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 03 18:04:48 2021 |
tree | f1b63f1371a30f72a3c0f601516b09eb73398996 | |
parent | 4117f121081b778435611749539c79983f322b72 [diff] |
[rust] Roll cxx to 1.0.57. This rolls cxx, cxxbridge_cmd and cxxbridge_macro Rust dependencies from 1.0.56 to 1.0.57. The only reason to do this is because they've taken one of our patches upstream, so we can delete one of our .patch files and slightly unfork. Procedure used: * Cherry-pick patchset 60 of https://chromium-review.googlesource.com/c/chromium/src/+/3212915 * Delete third_party/rust/cxx/v1/crate * Delete third_party/rust/cxxbridge_cmd/v1/crate * Delete third_party/rust/cxxbridge_macro/v1/crate * vpython3 tools/crates/crates.py download cxx 1.0 --security-critical no * vpython3 tools/crates/crates.py download cxxbridge-macro 1.0 --security-critical no * vpython3 tools/crates/crates.py download cxxbridge-cmd 1.0 --security-critical no * Reapply all patches from third_party/rust/{each of the three crates}/v1/patches * vpython3 tools/crates/crates.py gen (didn't make any changes) This CL also: * Deletes one of the patch files form third_party/rust/cxxbridge_cmd/v1/patches, because that patch has now been accepted upstream. * Renames one of the other patch files which was badly named. Change-Id: I2aa9f9ef49ab6c3a2b559b32da5e0b87a5c422f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3314392 Reviewed-by: Ćukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Adrian Taylor <adetaylor@chromium.org> Cr-Commit-Position: refs/heads/main@{#948061}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.