You've got a wonderful new platform that you'd like to run Chromium OS on, but have no idea how to get there from here? Fret not my fellow traveler, for this document shall be your guide. We promise it'll be a wondrous and enlightening journey.
An overlay is the set of configuration files that define how the build system will build a Chromium OS disk image. Configurations will be different depending on the board and architecture type, and what files a developer wants installed on a given disk image. Every command in the build process takes a required `--board` parameter, which developers should pass the overlay name to.
On your first run through this document for creating your first platform, you can skip the sections labeled (advanced). This will let you focus on the minimum bits to get running, and then you can revisit once you're more comfortable with things.
This guide covers doing a public build (one that will be released to the world). There is a separate guide (meant as an add-on to this one) for creating a private board. Setting up a private board is useful for when you want to keep your project details a secret before launch, or if your board contains proprietary drivers or firmware that can't be released publicly.
Possible board names follow a simple specification:
Settled on a name? Hopefully it's nifty.
Often times you will have a base/reference board on which you will build other boards/devices, and you want to customize each in ways that are incompatible with the others. The board variant framework is designed to handle this setup. Note: at the moment, the variant framework is only one level deep. So you cannot do a variant of a variant. A need for this has not been found, so we haven't worried about it.
When it comes to naming, you will take the existing reference board name and add on the new project's name separated by an underscore. Both projects must follow the naming convention laid out in the above section.
As an example, Google has a reference board named
Let's start by laying the ground work for the board. We won't worry about the fine details (like custom set of packages or flags or ...) at this point. We just want a board that the build system will recognize and be able to produce a generic set of artifacts. Once we have that, we'll start customizing things.
Be aware that we assume your board falls under one of the main (currently supported) architectures:
This is the main location for per-board customization. Let's start off with a simple overlay:
Most of these files are one or two lines. Let's go through them one at a time.
This file can be used to customize global settings for your board. In this first go, we'll leave it empty. It's ok ... we'll come back.
For standard architectures, you only need one line here. Pick the one that matches the architecture for your board.
Example file for an x86_64 board:
Note that if you do need more than one toolchain, you can list as many as you like (one per line). But the first entry must be the default one for your board.
Don't worry about the content of this file. Simply copy & paste what you see below, and then update the
This is the "base" profile (aka the default) for your board. It allows you to customize a wide array of settings. You really only need to create one file (the
Most commonly this directory is used to control USE and KEYWORDS on a per-package basis (via the
This will vary based on your architecture.
Example file for an x86_64 board:
Sometimes you will want to take an existing board and try out some tweaks on it. Perhaps you want to use a different kernel, or change one or two USE flags, or use a different compiler settings (like more debugging or technology like ASAN). You could create a board variant, but that is more for different boards, and is much more heavy handed.
To create a sub-profile, simply make a new directory under the profiles/ and name it whatever you like. Many Google based systems have one called
You should then create a
This says the sub-profile will start off using the existing base profile (so you don't have to duplicate all the settings you've already put into that directory). From here, you can add any files like you would any other profile directory.
Now to select this new profile, you use the
This folder contains scripts used during build_image, to tweak the packages that are allowed on the final image. The scripts of interest here are
Since we need some central location to store all the possible board names, we have the cros-board.eclass. It should be pretty self-explanatory.
We actively welcome commits to this file. Simply upload a CL to gerrit that adds your fun board and we'll gladly take a look for you.
Rather than create an entire hardware board from scratch every time a new project comes along, companies will often take existing projects and make tweaks to fit the new one. It's a common industry practice which allows for rapid expansion into more areas. Since these boards are pretty close to each other, it'd be annoying to have to duplicate the entire board settings just to make a handful of changes. The variant framework was designed to address this.
Basically, refer to the sections above for creating a new board overlay. However, this time name it slightly different. If the base board is named
You will still need to create at least these files (see the previous section for what to put into them):
Since your board should be all set up and ready to go, let's test it. All operations will be done inside the chroot (so run `cros_sdk` to get in first).
Those should both have worked and produced a generic build for that architecture (using your $BOARD name). Let's set about customizing the build now.
Note: as you make changes below to your overlay, re-running
This file contains a few key variables you'll be interested in. Since each of these can be a large topic all by themselves, this is just an overview.
You can set variables like you would in a shell script (
The kernel is automatically compiled & installed by the build system. In order to configure it, you have to start with a defconfig file as the base (it can later be refined by various USE flags). This value allows you to control exactly that.
You can specify the relative path (to the root of the kernel tree) to your defconfig. This is useful if you are using a custom kernel tree rather than the official Chromium OS Linux kernel tree.
Or you can specify a Chromium OS config base. We have one for each major platform/SoC that ships in an official Chrome OS device, and we have architecture generic configs. You can find the full list by browsing the chromeos/config/ directory in the kernel tree. Unlike a defconfig, splitconfigs are much smaller fragments which start with a common base and then enable/disable a few options relative to that.
The kernel build system normally detects what architecture you're using based on your overall profile. For example, if you have an amd64 board overlay setup, the build knows it should use ARCH=x86_64.
However, there arises edge cases where you want to run a kernel architecture that is different from the userland. For example, say you wanted to run a 64-bit x86_64 kernel, but you wanted to use a 32-bit i386 userland. If your profile is normally setup for an x86 system, you can set this variable to x86_64 to get a 64-bit kernel.
One of the strengths of the Gentoo distribution is that you can easily control general feature availability in your builds by changing your USE settings. For example, if you don't want audio, you can disable alsa & oss. Or if you don't want LDAP, you can disable that. All of the ebuild files (the package scripts used to build/install code) have logic to check each setting that is optional so you don't have to.
The downside, as you can imagine, is that with thousands and thousands of packages, the number of possible USE flags is vast. There are also some optional settings which only make sense with one or two packages (global vs local USE flags). So weeding through which USE flags exactly matter can be a bit of a monstrous task.
An extension to the USE flag system are so called USE-expanded variables. This helps reduce the global USE flag noise a bit by having specially named variables with specific meaning. In this case, we'll discuss device inputs (keyboards/mouse/etc...) and video outputs.
The exact driver availability (and naming convention) depends on what graphic system you intend to use. The X project tends to have the widest selection but is a larger overall install size, while DirectFB tends to have smaller selection of drivers but be much smaller. We'll focus on X here as that is the main system that Chromium supports.
Everyone likes optimizations. Faster is better, right? Here's the nuts and bolts of it.
This is for ARM targets only. Any value that GCC accepts to the -mfpu= flag is valid. This will be used by various packages (mostly Chromium) to select FPU-specific optimizations.
Typical values are neon and vfpv3-d16. If you have an ARMv7, pick between these two values. If you don't have an ARMv7, then you should already know the answer to this question :).
You should put compiler optimizations that target your specific cpu into this variable. Commonly, this means:
If you have flags that you want to use only when compiling C code, use this variable. Otherwise, things will default to
If you have flags that you want to use only when compiling C++ code, use this variable. Otherwise, things will default to
If you have flags that you want to send directly to the linker for all links, use this variable.
These should take the form as given to the compiler driver. i.e. use
You can find common settings in the GNU Linker manual.
Presumably you'd like to be able to easily (and cleanly) produce artifacts for your board. In our chromite repo, we have a tool called cbuildbot that takes care of all that for us. Normally it's run by buildbot on a waterfall to produce all the goodness, but there's no requirement that buildbot be the tool you use. You can even run it locally.
At any rate, you'll need to update this master file to add your new board configs. There are a few classes of configs to be familiar with:
The file should be largely self-documenting.
Sometimes you'll want to host large files or prebuilt binary packages for your repo, but you don't want to give out access to everyone in the world. You can great some boto config files, and the build scripts will automatically use them when they're found.
Create this file in the root of the overlay. This file stores the access credential (in cleartext) for the role account.
These are the ACL files used by gsutil to apply access for people. Used whenever you want to upload files and grant access to people who have the boto file.
The TXT format is documented in the gsutil FAQ. The JSON format is not yet used. Support for the XML format has been dropped.