mirror of
https://github.com/openai/codex.git
synced 2026-11-11 21:10:39 +00:00
zbarsky-openai
1099fe0694
## Why Windows MSVC builds relied on installed C++ toolchains, and V8 snapshot generation required native Windows execution. Cross-compiling V8 also needs a Windows snapshot generator to preserve Windows unwind metadata. ## What changed - Use the registered hermetic LLVM toolchain and declared Microsoft SDK for Windows MSVC builds, with static CRT linkage and the toolchain's declared `lld-link` for Rust. - Run Windows V8 snapshot generators natively or through `rules_wine` on Linux, preserving target CPU, OS, and sandbox settings. Keep separate archive and binding pairs for the workspace's ISO stdio ABI and the distributed MSVC stdio ABI. - Update build dependencies and bindgen, scope V8's Chromium libc++ settings to its own targets, and adapt native voice dependencies for clang-cl and Windows ARM64. - Build SQLite directly with Bazel and give `openssl-sys` an explicit build using Bazel's OpenSSL. - Remove build-worker source-directory dependencies from Bazel resource lookup, schema output discovery, and snapshot paths; embed assets in debug builds as well. GitOrigin-RevId: fd224d9d28d73a67baf90f6d73c6079d60f20351
20 lines
653 B
Python
20 lines
653 B
Python
"""Apply V8's private runtime policy after a generator's exec transition."""
|
|
|
|
load("@rules_cc//cc:cc_binary.bzl", "cc_binary")
|
|
load("@with_cfg.bzl", "with_cfg")
|
|
|
|
_PRIVATE_RUNTIME = select({
|
|
str(Label("//third_party/v8:use_rusty_v8_custom_libcxx")): True,
|
|
"//conditions:default": False,
|
|
})
|
|
|
|
# LLVM's flags are target-scoped. V8 generators intentionally share V8's
|
|
# private libc++ profile, but unrelated tools must keep their default runtime.
|
|
v8_cc_binary, _v8_cc_binary_internal = with_cfg(cc_binary).set(
|
|
Label("@llvm//config:nostdincxx"),
|
|
_PRIVATE_RUNTIME,
|
|
).set(
|
|
Label("@llvm//config:nostdlibxx"),
|
|
_PRIVATE_RUNTIME,
|
|
).build()
|