0
Files
src/buildtools
Takuto Ikuta 07250cd88b buildtools: Use clang_base_path for builtin modulemap file
This change addresses redefinition of module errors encountered when
building Clang locally with the `clang_base_path` set. Previously, using
the modulemap file under the third_party Clang directory along with a
locally built Clang caused conflicts due to the `-fbuiltin-module-map`
flag. This change resolves the conflict by using `clang_base_path` for
the builtin modulemap file, ensuring consistent module definitions.

Bug: 40440396
Change-Id: I6a928b914bfc4336bc619ad70ac694a107cd514c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6433627
Reviewed-by: Junji Watanabe <jwata@google.com>
Auto-Submit: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1443297}
2025-04-07 00:35:47 -07:00
..
2025-02-04 21:20:41 -08:00

This directory contains hashes of build tools used by Chromium and related
projects. The actual binaries are pulled from Google Storage, normally as part
of a gclient hook.

This directory also exists as a stand-alone git mirror at
https://chromium.googlesource.com/chromium/src/buildtools/.
That mirror exists so that the shared build tools can be shared between
the various Chromium-related projects without each one needing to maintain
their own versionining of each binary.

________________________
ADDING BINARIES MANUALLY

One uploads new versions of the tools using the 'gsutil' binary from the
Google Storage SDK:

  https://developers.google.com/storage/docs/gsutil

There is a checked-in version of gsutil as part of depot_tools.

To initialize gsutil's credentials:

  python ~/depot_tools/third_party/gsutil/gsutil config

  That will give a URL which you should log into with your web browser.

  Copy the code back to the command line util. Ignore the project ID (it's OK
  to just leave blank when prompted).