Clone this repo:
  1. 1d3d08e Generated files from "codesearch-gen-chromium-linux" build 1743, revision 1b743d52155038b6a5ecc164b4098e45612d1584 by Automatic Generated Files Sync · 2 hours ago master
  2. 7b208d4 Generated files from "codesearch-gen-chromium-linux" build 1742, revision bb89a0deef6e61a98da76c588348f0e06395fab0 by Automatic Generated Files Sync · 6 hours ago
  3. cdb0fde Generated files from "codesearch-gen-chromium-linux" build 1741, revision f386e8f4cc527392cf5708cdf30a8fe0cec4399d by Automatic Generated Files Sync · 10 hours ago
  4. 6e5f553 Generated files from "codesearch-gen-chromium-linux" build 1740, revision 5e5f476234f533f9cbe7c4616078bf540a948461 by Automatic Generated Files Sync · 14 hours ago
  5. 32767df Generated files from "codesearch-gen-chromium-linux" build 1739, revision 9eb45e53852762789fccb611636b7f2c83d62678 by Automatic Generated Files Sync · 18 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 (

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.