| commit | df24b82374fda6d85108b813573138ec5c7cedc6 | [log] [tgz] |
|---|---|---|
| author | James Robinson <jamesr@chromium.org> | Wed Oct 21 00:26:52 2015 -0700 |
| committer | James Robinson <jamesr@chromium.org> | Wed Oct 21 00:26:52 2015 -0700 |
| tree | 8130fbf8bce65c9bae866db32b6e67eeecead50c | |
| parent | b987b10683a5d2d56c2d286ccb2b972a26029578 [diff] |
Enter JIRI_ROOT to run jiri update, some hooks need it Some of the mojo hooks expect to run from the directory containing the Mojo 'src' directory since that's what gclient runhooks does. This needs to be fixed, but for now this just cd's into the appropriate directory so that the initial sync works. Change-Id: Ic3da19150410df3330c262b6eb7857ee5191b0c0
Contains the jiri manifest for the Mojo project
Mojo uses the jiri tool to manage repositories https://github.com/vanadium/go.jiri. This tool manages a set of repositories specified by a manifest. The $JIRI_ROOT variable determines where jiri and the Mojo repositories will be placed. To create a new Mojo checkout run this command with $JIRI_ROOT set to a path to hold the checkout. This path should not exist before running the script. The script requires that you have Go 1.4 or newer installed and on your PATH.
curl https://mojo.googlesource.com/mojo-manifest/+/master/bootstrap.sh?format=TEXT | base64 -d | bash
bootstrap.sh will populate the directory pointed to by $JIRI_ROOT and prompt you to add entries to your PATH.
Mojo requires several libraries and tools to build and run. Many are placed within the checkout and updated whenever jiri update runs, but some must be installed on the system. Run
$JIRI_ROOT/src/build/install-build-deps.sh
to install these packages.
See https://github.com/domokit/mojo for instructions on building and running tests for Mojo.