layout: doc title: “Set up your environment - Linux”

These instructions explain how Linux users set up their Cobalt development environment, clone 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.

Set up your workstation

  1. 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

  2. Install Node.js via nvm:

    $ 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

  3. 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

  4. Clone the Cobalt code repository. The following git command creates a cobalt directory that contains the repository:

    $ git clone https://cobalt.googlesource.com/cobalt

  5. Create a Python 3 virtual environment for working on Cobalt (feel free to use virtualenvwrapper instead):

    $ cd cobalt
$ python -m venv ~/.virtualenvs/cobalt_dev
$ source ~/.virtualenvs/cobalt_dev
$ pip install -r requirements.txt

  6. Install the pre-commit hooks:

    $ pre-commit install -t post-checkout -t pre-commit -t pre-push --allow-missing-config
$ git checkout -b <my-branch-name> origin/COBALT

Build and Run Cobalt

  1. 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 linux-x64x11.

    You can also use the -C command-line flag to specify a build_type. Valid build types are debug, devel, qa, and gold. If you specify a build type, the command finishes sooner. Otherwise, all types are built.

    $ cobalt/build/gyp_cobalt [-C <build_type>] <platform>

  2. Compile the code from the src/ directory:

    $ ninja -C out/<platform>_<build_type> <target_name>

    The previous command contains three variables:

    1. <platform> is the platform configuration that identifies the platform. As described in the Starboard porting guide, it contains a family name (like linux) and a binary variant (like x64x11), separated by a hyphen.
    2. <build_type> is the build you are compiling. Possible values are debug, devel, qa, and gold. These values are also described in the Starboard porting guide under the required file modifications for the gyp_configuration.gypi file.
    3. <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 cobalt, nplb, and all:
      • cobalt builds the Cobalt app.
      • nplb builds Starboard‘s platform verification test suite to ensure that your platform’s code passes all tests for running Cobalt.
      • all builds all targets.

    For example:

    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.

  3. 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.