Not only is it a bad idea to build directly from NFS for performance reasons, but builds won't actually work (builds use sudo, and root doesn't have access to your NFS mount, unless your NFS server has the no_root_squash option).
Wherever you place your source, you can still add a symbolic link to it from your home directory (this is suggested), like so:above.
After you've learned the basics, check out the links in the additional information section at the end of this document for You must have Linux to develop Chromium OS. However, we can't support everyone and their dog's Linux distro, so the only official supported environment is listed below.
If you want to help develop Chromium OS and you're looking for detailed information about how to get started, you're in the right place.
You can also use the quick-start guide instead, which gives just the basic steps that work for most people.
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.
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.
The chroot lives by default at Most of the commands that Chromium OS developers use on a day-to-day basis (including the commands to build a Chromium OS image) expect to be run from within the chroot.
You can enter the chroot by calling: This is the same command used to create the chroot, but if the chroot already exists, it will just enter.
For example, if you are using eclipse as an IDE, or gedit to edit a text file, you will need to run those programs outside the chroot. If you are desperate for emacs, try typing Building Chromium OS produces a disk image (usually just called an "image") that can be copied directly onto the boot disk of a computer intended to run Chromium OS.
Depending on the specifics of that computer, you may want different files in the disk image.
If you want to build on a branch, pass the branch name to repo init (e.g: chroot.