Changes

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 may be disabled by default at runtimeif 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 Manually set the <tt>gfx.webrender.enabled</tt> pref turned on by default instead of turned off by default.* Manually flip the or <tt>gfx.webrender.enabledall</tt> prefto true. You can do this from about:config, and it requires restarting the browser to take effect.

If you use mozilla-central(recommended), you have should use the option to request normal Gecko workflow and submit patches for review via Phabricator. If you really want, but your final changes must not land directlyyou can also submit PRs against the <tt>servo/webrender</tt> repository on Github, and should be submitted to one of the standalone WebRender repository. Git users can do this like so:  cd /path/to/m-c git format-core contributors will review and merge your patch into mozilla-pk central. The mozilla--relative=gfx/wr BASE_REVISION cd /path/to/central copy of webrender git checkout -b my_branch git am /path/to/mis considered canonical, and there is a periodic one-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 way sync from mozilla-central within a day or twoto Github.