Clone this repo:
  1. 6a10347 Generated files from "codesearch-gen-chromium-chromiumos" build 5797, revision 07aaf1f9a77b4023da1c9327d6fdf409a4d927aa by Automatic Generated Files Sync · 7 minutes ago master
  2. 392a6ae Generated files from "codesearch-gen-chromium-linux" build 6060, revision 07aaf1f9a77b4023da1c9327d6fdf409a4d927aa by Automatic Generated Files Sync · 11 minutes ago
  3. 508001b Generated files from "codesearch-gen-chromium-android" build 5118, revision 07aaf1f9a77b4023da1c9327d6fdf409a4d927aa by Automatic Generated Files Sync · 28 minutes ago
  4. 3a9ff32 Generated files from "codesearch-gen-chromium-win" build 3626, revision 0b749e1a9305769f0cc9e5cd199ff096f67c6f25 by Automatic Generated Files Sync · 46 minutes ago
  5. 312a0fa Generated files from "codesearch-gen-chromium-android" build 5117, revision 0b749e1a9305769f0cc9e5cd199ff096f67c6f25 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.