Platform/GFX/Quantum Render: Difference between revisions

Jump to navigation Jump to search

Platform/GFX/Quantum Render (view source)

Revision as of 14:04, 5 July 2019

384 bytes removed ,  5 July 2019
→‎Build instructions: Update workflows
(→‎Locally: Update for changes in bug 1558598)
(→‎Build instructions: Update workflows)
Line 25: Line 25:
== Build instructions ==
== Build instructions ==


Building is the same as building a regular mozilla-central build. In fact, any regular mozilla-central build should have WebRender built in, unless you explicitly disable it via <tt>ac_add_options --disable-webrender</tt>. However, WebRender will be disabled by default at runtime. You can enable it one of three ways:
Building is the same as building a regular mozilla-central build. However, WebRender may be disabled by default at runtime if you are running on hardware that we have not whitelisted. You can enable it one of three ways:
* Add <tt>ac_add_options --enable-webrender</tt> to your mozconfig. All this does is build with the <tt>gfx.webrender.enabled</tt> pref turned on by default instead of turned off by default.
* Manually set the <tt>gfx.webrender.enabled</tt> or <tt>gfx.webrender.all</tt> pref to true. You can do this from about:config, and it requires restarting the browser to take effect.
* Manually flip the <tt>gfx.webrender.enabled</tt> pref. You can do this from about:config, and it requires restarting the browser to take effect.
* Run firefox with <tt>MOZ_WEBRENDER=1</tt> as an environment variable. This will attempt to enable WebRender at runtime.
* Run firefox with <tt>MOZ_WEBRENDER=1</tt> as an environment variable. This will attempt to enable WebRender at runtime.


Line 39: Line 38:
   cargo build --features=capture,replay,pathfinder
   cargo build --features=capture,replay,pathfinder


If you use mozilla-central, you have the option to request review via Phabricator, but your final changes must not land directly, and should be submitted to the standalone WebRender repository. Git users can do this like so:
If you use mozilla-central (recommended), you should use the normal Gecko workflow and submit patches for review via Phabricator. If you really want, you can also submit PRs against the <tt>servo/webrender</tt> repository on Github, and one of the core contributors will review and merge your patch into mozilla-central. The mozilla-central copy of webrender is considered canonical, and there is a periodic one-way sync from mozilla-central to Github.
 
  cd /path/to/m-c
  git format-patch -pk --relative=gfx/wr BASE_REVISION
  cd /path/to/webrender
  git checkout -b my_branch
  git am /path/to/m-c/0*
  git push my_branch
 
You should then ping a bors operator to carry your apply your r+ to the GitHub PR. Once your change lands in upstream WebRender, it will be synced to mozilla-central within a day or two.


=== Testing third-party rust library changes ===
=== Testing third-party rust library changes ===
Kats
Confirmed users
586

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1214640"

Navigation menu