These instructions explain how Linux users set up their Cobalt development environment, fetch a copy of the Cobalt code repository, and build a Cobalt binary. Note that the binary has a graphical client and must be run locally on the machine that you are using to view the client. For example, you cannot SSH into another machine and run the binary on that machine.
Choose where you want to put the
depot_tools directory, which is used by the Cobalt code. An easy option is to put them in
~/depot_tools. Clone the tools by running the following command:
$ cd ~/ $ git clone https://cobalt.googlesource.com/depot_tools
depot_tools directory to the end of your
PATH variable. We recommend adding something like this to your
Run the following command to install packages needed to build and run Cobalt on Linux:
$ sudo apt install -qqy --no-install-recommends pkgconf ninja-build bison \ yasm binutils clang libgles2-mesa-dev mesa-common-dev libpulse-dev \ libavresample-dev libasound2-dev libxrender-dev libxcomposite-dev
Install Node.js via
$ export NVM_DIR=~/.nvm $ export NODE_VERSION=12.17.0 $ curl --silent -o- https://raw.githubusercontent.com/creationix/nvm/v0.35.3/install.sh | bash $ . $NVM_DIR/nvm.sh \ && nvm install --lts \ && nvm alias default lts/* \ && nvm use default
Install ccache to support build acceleration. ccache is automatically used when available, otherwise defaults to unaccelerated building:
$ sudo apt install -qqy --no-install-recommends ccache
We recommend adjusting the cache size as needed to increase cache hits:
$ ccache --max-size=20G
Clone the Cobalt code repository. The following
git command creates a
cobalt directory that contains the repository:
$ git clone https://cobalt.googlesource.com/cobalt
Build the code by navigating to the
src directory in your new
cobalt directory and running the following command. You must specify a platform when running this command. On Ubuntu Linux, the canonical platform is
You can also use the
-C command-line flag to specify a
build_type. Valid build types are
gold. If you specify a build type, the command finishes sooner. Otherwise, all types are built.
$ cobalt/build/gyp_cobalt [-C <build_type>] <platform>
Compile the code from the
$ ninja -C out/<platform>_<build_type> <target_name>
The previous command contains three variables:
<platform>is the platform configuration that identifies the platform. As described in the Starboard porting guide, it contains a
linux) and a
x64x11), separated by a hyphen.
<build_type>is the build you are compiling. Possible values are
gold. These values are also described in the Starboard porting guide under the required file modifications for the
<target_name>is the name assigned to the compiled code and it is used to run the code compiled in this step. The most common names are
cobaltbuilds the Cobalt app.
nplbbuilds Starboard‘s platform verification test suite to ensure that your platform’s code passes all tests for running Cobalt.
allbuilds all targets.
ninja -C out/linux-x64x11_debug cobalt
This command compiles the Cobalt
debug configuration for the
linux-x64x11 platform and creates a target named
cobalt that you can then use to run the compiled code.
Run the compiled code to launch the Cobalt client:
# Note that 'cobalt' was the <target_name> from the previous step. $ out/linux-x64x11_debug/cobalt [--url=<url>]
The flags in the following table are frequently used, and the full set of flags that this command supports are in cobalt/browser/switches.cc.