chromium/src
0
Fork 0
Code Activity

Remove the apply_patches.sh step in crate rolling

Browse Source 
Patches are automatically applied on new downloads by gnrt vendor. This
is described elsewhere in the doc already.

R=adetaylor@chromium.org

Fixed: 351040921
Change-Id: Iaa704ed3acdc3bc54e6cb356c295465876a90a42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5678219
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Auto-Submit: danakj <danakj@chromium.org>
Reviewed-by: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1323395}
This commit is contained in:
danakj
2024-07-04 16:30:16 +00:00
committed by Chromium LUCI CQ
parent c38d80592a
commit 784fcc3bfd
1 changed files with 0 additions and 4 deletions

4
docs/rust.md

@ -178,10 +178,6 @@ version, then follow the steps below:
* `git add -f third_party/rust/chromium_crates_io/vendor`
* The `-f` is important, as files may be skipped otherwise from a
`.gitignore` inside the crate.
1. If a crate in `//third_party/rust/chromium_crates_io/patches` was updated
as part of vendoring, then reapply patches to it:
* Go to the `//third_party/rust/chromium_crates_io` directory.
* `./apply_patches.sh` (this currently requires linux).
1. Generate the `BUILD.gn` files
* `vpython3 ./tools/crates/run_gnrt.py gen`
* Or, directly through (nightly) cargo: