Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-19 00:05:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Bug 1328910 - Update README.webrender to fix WR update process. r=gfx? and DONTBUILD

Browse Source 
MozReview-Commit-ID: EdKgaHr1Z3E
This commit is contained in:
Kartikaya Gupta 2017-01-05 11:27:41 -05:00
parent 7aa28bb943
commit 691689628f
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.webrender
View File

@ -27,22 +27,25 @@ For a debug webrender build:
What if you have to make changes to webrender itself?
1) Update your graphics branch checkout to the latest code on the
graphics branch
graphics branch
2) Check out and update the webrender repo to the version you want
3) Copy over the webrender and webrender_traits folders into gfx/.
3) Copy over the webrender and webrender_traits folders into gfx/ and update
the "latest commit" information at the bottom of this file.
4) If you need to modify webrender_bindings/Cargo.toml to include or remove
features, do so now.
4) Commit your changes to the graphics branch locally
5) Run |mach vendor rust| to update the rust dependencies in third_party/rust
6) Commit the vendored changes locally
7) Build and test. You may need to make changes in bindings.rs or on
5) Go into toolkit/library/rust and run |cargo update --aggressive -p webrender|.
Do the same in toolkit/library/gtest/rust. This will update the corresponding
Cargo.lock files with the latest webrender dependencies.
6) Run |mach vendor rust| to update the rust dependencies in third_party/rust
7) Commit the vendored changes locally
8) Build and test. You may need to make changes in bindings.rs or on
the C++ side depending on what changed in webrender. This can
potentially be quite tricky if you don't fully understand the API
changes on the webrender side. In this step, try to not use your new
features yet, just get the build working with the minimal changes.
8) Commit the changes locally from step 7, and push everything to the
9) Commit the changes locally from step 7, and push everything to the
graphics branch.
9) Update the webrender commit below.
10) Now you have an update webrender with the new features you wanted,
so you can write gecko code against them.