Clone this repo:
  1. 94fed57 Generated files from "codesearch-gen-chromium-chromiumos" build 3138, revision 042919888010b41fda182356bf27c4fa2cb15f71 by Automatic Generated Files Sync · 2 hours ago master
  2. 7e54827 Generated files from "codesearch-gen-chromium-android" build 2230, revision 042919888010b41fda182356bf27c4fa2cb15f71 by Automatic Generated Files Sync · 2 hours ago
  3. 0dca4a4 Generated files from "codesearch-gen-chromium-linux" build 3331, revision 042919888010b41fda182356bf27c4fa2cb15f71 by Automatic Generated Files Sync · 2 hours ago
  4. cf943e0 Generated files from "codesearch-gen-chromium-chromiumos" build 3137, revision 5220d0e27bde79cdb393de6f20ca0591d44504ac by Automatic Generated Files Sync · 6 hours ago
  5. a9bba7a Generated files from "codesearch-gen-chromium-android" build 2229, revision 5220d0e27bde79cdb393de6f20ca0591d44504ac by Automatic Generated Files Sync · 6 hours ago

What's this?

This git repository exists to allow the source files generated during a Chromium build to be indexed by code search (https://cs.chromium.org).

You do not need to clone this repository, and it is not used in any way during a build.

How does it work?

A build slave regularly does a full Linux build of Chromium, and afterwards pushes all the generated files (from the src/out/Debug/gen directory) into this git repository.

Another build slave maintains a git repository containing gitlinks (git submodules) representing the dependencies specified in Chromium's DEPS file. That script also adds a gitlink named “out” pointing to this repository.

The code search crawler indexes that gitlink repository following all the gitlinks inside, which eventually leads it here and allows it to index the generated code.