Chromium Code Reviews (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out

Unified Diff: docs/

Issue 2490533002: Ozone documentation: Take into account recent changes in Linux Desktop (Closed)
Patch Set: Remove content_shell from working Linux Desktop targets. Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/
diff --git a/docs/ b/docs/
index 965c3320dcb49e59ffaf170dd466abc30a07980a..5812d3fd766aad4a6733ee9b6d1d34895429a6ef 100644
--- a/docs/
+++ b/docs/
@@ -160,10 +160,29 @@ Then to run for example the headless platform:
-### Linux Desktop - ([bug](
+### Linux Desktop - ([waterfall](
+Support for Linux Desktop is currently [in-progress](
-This is not supported by any of the in-tree platforms. Please see above and try
-a ChromeOS or embedded build for now.
+The following targets are currently working:
+* various unit tests
+* `chrome`
+To build `chrome`, do this from the `src` directory:
+``` shell
+gn args out/OzoneLinuxDesktop --args="use_ozone=true enable_package_mash_services=true"
+ninja -C out/OzoneLinuxDesktop chrome
+Then to run for example the X11 platform:
+``` shell
+./out/OzoneLinuxDesktop/chrome --ozone-platform=x11 \
+ --disable-setuid-sandbox \
+ --mash
+Note: You may need to apply [this patch]( to avoid missing ash resources during chrome execution.
### GN Configuration notes
@@ -242,18 +261,16 @@ and then partially upstreamed.
It is still actively being developed in the chromium tree, feel free to discuss
with us on, `#ozone-wayland` channel or on `ozone-dev`.
-In order to run an Ozone build of `chrome`, you currently (2016/10/28)
-need to compile it for ChromeOS, where software rendering is not allowed.
-Also, accelerated rendering only works in Ozone/Wayland when the UI and GPU
-components are running in the same process. Below are some quick build & run
-instructions. It is assumed that you are launching `chrome` from a Wayland
-environment such as `weston`.
+Below are some quick build & run instructions. It is assumed that you are
+launching `chrome` from a Wayland environment such as `weston`. Apply
+[this patch]( and execute the
+following commands:
``` shell
-gn args out/OzoneWayland --args="use_ozone=true ozone_platform_wayland=true target_os=\"chromeos\""
+gn args out/OzoneWayland --args="use_ozone=true enable_package_mash_services=true"
ninja -C out/OzoneWayland chrome
./out/OzoneWayland/chrome --ozone-platform=wayland \
- --in-process-gpu \
+ --mash \
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698