Use the following command: (shell) cros chrome-sdk -chrome-branding -board=$BOARD -log-level=info Use it for performance testing, not for debugging. official doesn't involve branding, instead it enables an additional level of optimization and removes development conveniences like runtime stack traces. Googlers: Use -chrome-branding if you need a branded Chrome build including resources and components from src-internal to work on internal features like ARC and assistant. Use this option to persist changes made to a previous session's gn args. -nogn-gen Do not run ‘gn gen’ automatically.-log-level=info Sets the log level to ‘info’ or ‘debug’ (default is ‘warn’).-gn-extra-args='extra_arg=foo other_extra_arg=bar' For setting extra gn args, e.g.-official Enables the official build level of optimization.-chrome-branding Sets up Simple Chrome to build and deploy the internal Chrome instead of Chromium.
You‘ll also need to pull in Android native toolchain dependencies to build ARC++ support libraries. When prompted for a project ID, enter 134157665460 (this is the Chrome OS project ID). ( Googlers: Use your account.) Otherwise steps below may run slowly and fail with “Login Required” from gsutil. Use depot_tools/gsutil.py and run gsutil.py config to set the authentication token. gclient file the official API keys will be set up automatically.
Googlers: See chrome build instructions to get the internal source.You'll need to put them in your out_$BOARD/Release/args.gn file, see below. In order to sign in to Chrome OS you must have Google API keys:
Inside the cros_sdk chroot on your workstationĬheck out a copy of the Chrome source code and depot_tools. Inside the chrome-sdk SDK shell on your workstation Outside the chroot and SDK shell on your workstation
Install the test image onto your device.