Now that you've synced down the source code, you need to create this chroot. The command with --bootstrap takes about half an hour to run on a four core machine.It compiles quite a bit of software, which it installs into your chroot, and downloads some additional items (around 300MB).
NOTE: if you want to run a single command in the chroot (rather than entering the chroot), prefix that command with Calling this will also install a chroot, if you don't have one yet, for example by not following the above.
While in the chroot you will see a special "(cros-chroot)" prompt to remind you that you are there: You generally cannot run programs on your filesystem from within the chroot.
This starts you out with a minimum amount of source code.
This isn't a particularly well tested configuration and has been known to break from time-to-time, so we usually recommend against it.) Googlers: See goto/chromeos-building for internal notes.
Per this thread, linking Chrome requires somewhere between 8 GB and 28 GB of RAM as of March 2017; you may be able to get by with less at the cost of slower builds with adequate swap space.
Seeing an error like Sources need to be world-readable to properly function inside the chroot (described later).For that reason, the last digit of your umask should not be higher than 2, eg. Many distros have this by default, Ubuntu, for instance, does not.It is essential to put the following line into your ~/.bashrc file before you checkout or sync your place your code somewhere else.Make sure you have followed the gerrit credentials setup instructions here.(Note: If you are on a slow network connection or have low disk space, you can use the minilayout option below.The tasks are grouped into the following sections: If you're a Chromium OS developer, YOU SHOULD UPDATE THIS DOCUMENT and fix things as appropriate.