Clone this repo:
  1. ceb1623 Generated files from "codesearch-gen-chromium-chromiumos" build 6183, revision 0cc2b3153e5b43907f46af25fca3b2fa4a82da1d by Automatic Generated Files Sync · 2 minutes ago master
  2. ca2523a Generated files from "codesearch-gen-chromium-linux" build 6452, revision 0cc2b3153e5b43907f46af25fca3b2fa4a82da1d by Automatic Generated Files Sync · 8 minutes ago
  3. a336143 Generated files from "codesearch-gen-chromium-win" build 3997, revision 21a0edd1ded0244cd04af082b5c7945655759ae0 by Automatic Generated Files Sync · 3 hours ago
  4. bf02562 Generated files from "codesearch-gen-chromium-android" build 5521, revision 21a0edd1ded0244cd04af082b5c7945655759ae0 by Automatic Generated Files Sync · 4 hours ago
  5. 0deea25 Generated files from "codesearch-gen-chromium-chromiumos" build 6182, revision 21a0edd1ded0244cd04af082b5c7945655759ae0 by Automatic Generated Files Sync · 4 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.