Clone this repo:
  1. 4920180 Generated files from "codesearch-gen-chromium-win" build 2672, revision b2f60c9436cf198532ac9826415df7f505ab19fb by Automatic Generated Files Sync · 40 minutes ago master
  2. 9343675 Generated files from "codesearch-gen-chromium-chromiumos" build 4458, revision 43ed4581c0e1f963b3accaa71c6f90f2e33e9aa4 by Automatic Generated Files Sync · 71 minutes ago
  3. 4e4d2d4 Generated files from "codesearch-gen-chromium-linux" build 4652, revision 43ed4581c0e1f963b3accaa71c6f90f2e33e9aa4 by Automatic Generated Files Sync · 71 minutes ago
  4. 52ac45d Generated files from "codesearch-gen-chromium-android" build 3550, revision 43ed4581c0e1f963b3accaa71c6f90f2e33e9aa4 by Automatic Generated Files Sync · 83 minutes ago
  5. a20fa6f Generated files from "codesearch-gen-chromium-win" build 2671, revision 6f10930c47ad9475d82a398d6a33c6f5742c0a71 by Automatic Generated Files Sync · 3 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.