Clone this repo:
  1. c0f1a37 Generated files from "codesearch-gen-chromium-chromiumos" build 3782, revision 77ba1a3375c9fb4d4edb7e663035c48775175b2d by Automatic Generated Files Sync · 17 minutes ago master
  2. 77db2d6 Generated files from "codesearch-gen-chromium-linux" build 3976, revision 77ba1a3375c9fb4d4edb7e663035c48775175b2d by Automatic Generated Files Sync · 21 minutes ago
  3. 730a317 Generated files from "codesearch-gen-chromium-android" build 2874, revision 77ba1a3375c9fb4d4edb7e663035c48775175b2d by Automatic Generated Files Sync · 27 minutes ago
  4. 516d3e9 Generated files from "codesearch-gen-chromium-chromiumos" build 3781, revision 816d9b6046dc999532f4db0e9ca75a1bb0d6c9fd by Automatic Generated Files Sync · 2 hours ago
  5. d2d8ef0 Generated files from "codesearch-gen-chromium-linux" build 3975, revision 816d9b6046dc999532f4db0e9ca75a1bb0d6c9fd by Automatic Generated Files Sync · 2 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.