Previously, //v8:v8 exposed :v8_base via public_deps, which propagated
V8-internal codegen dependencies (such as :run_torque) to all downstream
embedder targets. In Chromium builds, this forced over 20,000 non-V8 C++
files (e.g. in Blink and Content) to wait for Torque code generation
before starting compilation, even though they only include public V8
headers. Additionally, :torque_base transitively depended on :v8_tracing
via :v8_headers and :cppgc_headers, blocking Torque compiler compilation
on Perfetto proto/IPC codegen.
To unblock downstream C++ compilation and allow :torque_base to compile
earlier:
1. Move :v8_base and :v8_snapshot from public_deps to deps in //v8:v8
(and :cppgc_base in //v8:cppgc), and add inspector_headers to expose
public inspector headers without pulling in internal Torque outputs.
2. Add public = [] to v8_base_without_compiler and v8_compiler so their
internal public_deps (like :run_torque) do not leak into v8.harddeps.
3. Move v8-trace-categories.h and :v8_tracing from v8_headers to
cppgc_base, and split v8_libplatform_headers from v8_libplatform so
torque_base does not wait on Perfetto codegen.
NO_IFTTT=GN-specific dependency restructuring; v8_headers_files updated in BUILD.bazel
Bug: 563098656
Change-Id: I62e55734f6c2f8c3dd551aec6ef18f031b059ffd
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/8474951
Commit-Queue: Simon Zünd <szuend@chromium.org>
Auto-Submit: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Simon Zünd <szuend@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/main@{#110123}
Takuto Ikuta
db3548f67b