A few weeks ago, Google announced that Chrome OS will be ready for release this fall. Like many Google products, Chrome OS is designed to be a game changer. There are no desktop applications, as we typically think of them. Instead, the entire user experience happens within the browser. Naturally, some people think this is ridiculous while others see it as the natural evolution of technology. The success or failure of Chrome OS might even be a major factor in determining whether or not that evolution happens. If you’d like to find out for yourself, here’s how to build the Chrome OS image.
Technically, we’re compiling Chromium OS, but the two terms are interchangeable within the scope of this guide.
What to Expect
We’re building a full operating system, not just an individual application, so you can expect more in terms of steps involved and time until completion. That said, it’s not a very difficult process, and most of the time involved will be waiting for downloads to finish and code to compile. It would be helpful to have prior experience compiling software on Linux, such as what’s described here. Depending on Internet and CPU speed, this process could take anywhere from 1-4 hours, but again, most of that time is spent waiting on downloads and compilation.
To perform the build properly, you will need to be running a 64-bit Linux install. 32-bit is not currently supported as a build environment, but that may change in the future. Google recommends Ubuntu for this purpose, so that is the OS assumed by the rest of this guide.
To install all software needed to properly build Chrome OS, just run the following from a terminal:
One thing that’s not in Ubuntu’s repositories is Google’s depot-tools package, but that’s a simple download and extraction away. Click here to get the tar.gz file, and extract it to your home directory. You should now have a directory called depot_tools within your home.
Now just add that location to your command path with:
Getting the Source Code
We’re going to create a chrome directory within your home to hold all the files for this build, then download the source code. It’ll be downloading a few hundred megabytes, so this is probably going to take a while.
Building the Source
In these next steps, we’re going to start the scripts that will actually build the code into usable binaries. The following commands will compile the source for a generic x86 processor, something that should run pretty well on your average CPU, but not optimized for any particular one.
At this point you should have a prompt similar to the following:
And now to perform the real meat of this process, the actual build.
If all went well, you’re ready for the final step…
Generating the Image
Finally, we’ve got to create an image of this system that we can use on our devices or virtual machines. To build the base image, return to your shell and enter…
… and sit down for some tea while you wait.
When finished, you’ll get some info on exactly where the image file was placed, along with some handy details on how to automatically generate a more specific image type for your needs, such as USB, VMWare or Virtualbox.
Before you can run those scripts, you’ll need to exit the chroot environment by typing
In this example, we’re going to build for Virtualbox. Make sure you replace the directory location with the one on your system.
VMWare/Virtualbox: Unfortunately, there appears to be a bug in some versions of the image_to_vmware script that also affects the image_to_virtualbox script. If you get an error about “Can’t open /usr/lib/shflags”, then you’ve got to do a quick edit of image_to_vmware.sh and change the line
USB: It seems the image_to_usb script does not like to have a tilde (~) in the from flag. If you get errors saying that it can’t find the image, make sure to use the full path in the from flag.
Will Chrome OS be the next big thing or is it a step in the wrong direction?