Clone this repo:
  1. 156fe3f Generated files from "codesearch-gen-chromium-chromiumos" build 8254, revision 4c2f98bd47f8f804da47c6db4f4dc8d4847c9fb9 by Automatic Generated Files Sync · 2 hours ago master
  2. 9dee195 Generated files from "codesearch-gen-chromium-android" build 7591, revision 4c2f98bd47f8f804da47c6db4f4dc8d4847c9fb9 by Automatic Generated Files Sync · 3 hours ago
  3. ffddf1b Generated files from "codesearch-gen-chromium-linux" build 8521, revision 4c2f98bd47f8f804da47c6db4f4dc8d4847c9fb9 by Automatic Generated Files Sync · 3 hours ago
  4. 60b8f98 Generated files from "codesearch-gen-chromium-win" build 5892, revision 4de7b77b4bb3dc61df6d4911e781d030d3b88f9b by Automatic Generated Files Sync · 5 hours ago
  5. 01afc69 Generated files from "codesearch-gen-chromium-chromiumos" build 8253, revision 4de7b77b4bb3dc61df6d4911e781d030d3b88f9b 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.