core/core-agent-ide
8
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
core-agent-ide/third_party/v8
History
Channing Conger ded7854f09
V8 Bazel Build (#15021) 
Alternative approach, we use rusty_v8 for all platforms that its
predefined, but lets build from source a musl v8 version with bazel for
x86 and aarch64 only. We would need to release this on github and then
use the release.
2026-03-19 18:05:23 -07:00
..
BUILD.bazel V8 Bazel Build (#15021) 2026-03-19 18:05:23 -07:00
README.md V8 Bazel Build (#15021) 2026-03-19 18:05:23 -07:00
v8_crate.BUILD.bazel V8 Bazel Build (#15021) 2026-03-19 18:05:23 -07:00

README.md

rusty_v8 Release Artifacts

This directory contains the Bazel packaging used to build and stage target-specific rusty_v8 release artifacts for Bazel-managed consumers.

Current pinned versions:

  • Rust crate: v8 = =146.4.0
  • Embedded upstream V8 source: 14.6.202.9

The generated release pairs include:

  • //third_party/v8:rusty_v8_release_pair_x86_64_apple_darwin
  • //third_party/v8:rusty_v8_release_pair_aarch64_apple_darwin
  • //third_party/v8:rusty_v8_release_pair_x86_64_unknown_linux_gnu
  • //third_party/v8:rusty_v8_release_pair_aarch64_unknown_linux_gnu
  • //third_party/v8:rusty_v8_release_pair_x86_64_unknown_linux_musl
  • //third_party/v8:rusty_v8_release_pair_aarch64_unknown_linux_musl
  • //third_party/v8:rusty_v8_release_pair_x86_64_pc_windows_msvc
  • //third_party/v8:rusty_v8_release_pair_aarch64_pc_windows_msvc

Each release pair contains:

  • a static library built from source
  • a Rust binding file copied from the exact same v8 crate version for that target

Do not mix artifacts across crate versions. The archive and binding must match the exact pinned v8 crate version used by this repo.

The dedicated publishing workflow is:

  • .github/workflows/rusty-v8-release.yml

That workflow currently stages musl artifacts:

  • librusty_v8_release_x86_64-unknown-linux-musl.a.gz
  • librusty_v8_release_aarch64-unknown-linux-musl.a.gz
  • src_binding_release_x86_64-unknown-linux-musl.rs
  • src_binding_release_aarch64-unknown-linux-musl.rs

During musl staging, the produced static archive is merged with the target's LLVM libc++ and libc++abi static runtime archives. Rust's musl toolchain already provides the matching libunwind, so staging does not bundle a second copy.