We even have CSS Flexbox now, hooray!
See the Cobalt Subset specification for more details on which tags, properties, and Web APIs are supported in Cobalt.
All source locations are specified relative to
src/ (this directory).
base/ - Chromium's Base library. Contains common utilities, and a light platform abstraction, which has been superceded in Cobalt by Starboard.
net/ - Chromium's Network library. Contains enough infrastructure to support the network needs of an HTTP User-Agent (like Chromium or Cobalt), an HTTP server, a DIAL server, and several abstractions for networking primitives. Also contains SPDY and QUIC implementations.
cobalt/ - The home of all Cobalt application code. This includes the Web Implementation, Layout Engine, Renderer, and some other Cobalt-specific features.
cobalt/build/ - The core build generation system,
gyp_cobalt, and configurations for supported platforms. (NOTE: This should eventually be mostly moved into
cobalt/doc/ - Contains a wide range of detailed information and guides on Cobalt features, functionality and best practices for Cobalt development.
cobalt/media/ - Chromium's Media library. Contains all the code that parses, processes, and manages buffers of video and audio data. It send the buffers to the SbPlayer implementation for playback.
starboard/ - Cobalt‘s porting layer. Please see Starboard’s
README.md for more detailed information about porting Starboard (and Cobalt) to a new platform.
third_party/ - Where all of Cobalt‘s third-party dependencies live. We don’t mean to be perjorative, we love our third-party libraries! This location is dictated by Google OSS release management rules...
third_party/starboard/ - The location for third-party ports. This directory will be scanned automatically by gyp_cobalt for available Starboard ports.
See the below reference port setup guides for more details:
Cobalt has four build optimization levels, going from the slowest, least optimized, with the most debug information at the top (debug) to the fastest, most optimized, and with the least debug information at the bottom (gold):
When building for release, you should always use a gold build for the final product.
This is a fork of the chromium repository at http://git.chromium.org/git/chromium.git