This page explains the steps necessary to do a fresh setup of Cloud9 on your machine. For your convenience, these steps have been also put together in a setup automation script, courtesy of Andrei Costin.
Cloud9 is made out of components that reside in different repositories, either under DSLab administration, or outside on the Internet. The repositories are put together with the help of an utility called depot_tools, originally developed for Google's Chromium project.
Cloud9 works on 64-bit Linux distributions only. It has been tested on Ubuntu 10.04, 10.10, and 11.10, and it should work with other distros as well.
Install the required Ubuntu development packages:
Install Google's glog library:
The last command is necessary to force the linker cache to pick up the new library addition.
Create a fresh directory for the Cloud9 installation. We call this directory $CLOUD9_ROOT. In your terminal, execute the following:
The gclient config command generates in the current directory a .gclient file describing the managed repository:
The gclient sync command takes a lot of time. It checks out the entire Cloud9 code, and executes several one-time hooks:
The Cloud9 code structure is documented here.
Cloud9 uses Chromium's gyp for building its internal LLVM bitcode targets, and some other components. We are in the process of converting the entire Cloud9 codebase to gyp. Before that happens, you still need to perform manually the following building steps:
NOTE 1: If you get a linking error related to missing Google glog symbols, make sure that you don't have installed the Gold version of the system's Binutils (remove them using
NOTE 2: Due to a bug in the build system, you may get missing header errors in the klee/data subdirectory. If this is the case, run first