Mojo is an effort to extract a common platform out of Chrome's renderer and plugin processes that can support multiple types of sandboxed content, such as HTML, Pepper, or NaCl.
The instructions below only need to be done once. Note that a simple "git clone" command is not sufficient to build the source code because this repo uses the gclient command from depot_tools to manage most third party dependencies.
-
Download depot_tools and make sure it is in your path:
http://www.chromium.org/developers/how-tos/install-depot-tools -
[Googlers only] Install Goma in ~/goma.
-
Create a directory somewhere for your checkout (preferably on an SSD), cd into it, and run the following commands:
$ fetch mojo # append --target_os=android to include Android build support.
$ cd src
# Or install-build-deps-android.sh if you plan to build for Android.
$ ./build/install-build-deps.sh
$ mojo/tools/mojob.py gn
The "fetch mojo" command does the following:
- creates a directory called 'src' under your checkout directory
- clones the repository using git clone
- clones dependencies with gclient sync
install-build-deps.sh installs any packages needed to build, then mojo/tools/mojob.py gn runs gn args and configures the build directory, out/Debug.
If the fetch command fails, you will need to delete the src directory and start over.
Build Mojo for Linux by running:
$ ninja -C out/Debug -j 10
(If you are a Googler, see the section at the end of this document for faster builds.)
You can also use the mojob.py script for building. This script automatically calls ninja and sets -j to an appropriate value based on whether Goma is present. You cannot specify a target name with this script.
mojo/tools/mojob.py build
Run a demo:
mojo/tools/mojo_demo.py --browser
Run the tests:
mojo/tools/mojob.py test
Create a release build:
mojo/tools/mojob.py gn --release
mojo/tools/mojob.py build --release
mojo/tools/mojob.py test --release
You can update your repo like this. The order is important. You must do the git pull first because gclient sync is dependent on the current revision.
# Fetch changes from upstream and rebase the current branch on top
$ git pull --rebase
# Update all modules as directed by the DEPS file
$ gclient sync
You do not need to rerun gn gen out/Debug or mojo/tools/mojob.py gn. Ninja will do so automatically as needed.
With git you should make all your changes in a local branch. Once your change is committed, you can delete this branch.
Create a local branch named "mywork" and make changes to it.
cd src
git new-branch mywork
vi ...
Commit your change locally (this doesn't commit your change to the SVN or Git server)
git commit -a
Fix your source code formatting
$ git cl format
Upload your change for review
$ git cl upload
Respond to review comments
See Contributing code for more detailed git instructions, including how to update your CL when you get review comments. There's a short tutorial that might be helpful to try before your first change: C++ in Chromium 101.
To land a change after receiving LGTM:
$ git cl land
Don't break the build! Waterfall is here: http://build.chromium.org/p/client.mojo/waterfall
To build for Android, first make sure you've downloaded build support for Android, which you would have done by adding --target_os=android when you ran fetch mojo. If you didn't do that, there's an easy fix. Edit the file .gclient in your root Mojo directory (the parent directory to src.) Add this line at the end of the file:
target_os = [u'android']
Bring in android specific build dependencies:
$ build/install-build-deps-android.sh
Pull down all of the packages with this command:
$ gclient sync
Prepare the build directory for Android:
$ mojo/tools/mojob.py gn --android
Finally, perform the build. The result will be in out/android_Debug:
$ mojo/tools/mojob.py build --android
If you see javac compile errors, make sure you have an up-to-date JDK: https://code.google.com/p/chromium/wiki/AndroidBuildInstructions#Install_Java_JDK
Because the dart analyzer is a bit slow, we don't run it unless the user specifically asks for it. To run the dart analyzer against the list of dart targets in the toplevel BUILD.gn file, run:
$ mojo/tools/mojob.py dartcheck
If you're a Googler, you can use Goma, a distributed compiler service for open-source projects such as Chrome and Android. The instructions below assume that Goma is installed in the default location (~/goma).
To enable Goma, update your "args.gn" file. Open the file in your editor with this command:
$ gn args out/Debug
Add this line to the end of the file:
use_goma = true
After you close the editor, the "gn args" command will automatically run "gn gen out/Debug" again.
Now you can dramatically increase the number of parallel tasks:
$ ninja -C out/Debug -j 1000
-
Prerequisites:
- Before you start, you'll need a device with an unlocked bootloader, otherwise you won't be able to run adb root (or any of the commands that require root). For Googlers, follow this link and follow the instructions before returning to this page.
- Ensure your device is running Lollipop and has an userdebug build.
- Set up environment for building on Android. This sets up the adb path, etc. You may need to remove /usr/bin/adb.
source build/android/envsetup.sh -
Build changed files:
mojo/tools/mojob.py build --android -
Run Mojo Shell on the device (this will also push the built apk to the device):
mojo/tools/android_mojo_shell.py mojo:spinning_cube
If this fails and prints:
error: closed error: closed
... then you may not have a new enough build of Android on your device. You need L (Lollipop) or later.
- If you get a crash you won't see symbols. Use tools/android_stack_parser/stack to map back to symbols, e.g.:
adb logcat | ./tools/android_stack_parser/stack
-
Build the mojo target as described under link.
-
Run Mojo Shell:
./out/Debug/mojo_shell mojo:spinning_cube -
Optional: Run Mojo Shell with an HTTP server
cd out/Debug python -m SimpleHTTPServer 4444 & ./mojo_shell --origin=http://127.0.0.1:4444 --disable-cache mojo:spinning_cube