3 people b0ffed7c3e Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652) ...

This let's you point Bazel at an installed toolchain or download one of
our release archives. When you do, it will configure itself as a C++
Bazel toolchain. This toolchain works reasonably well, but doesn't cache
the C++ runtimes, and so linking is inefficient. The next step will be
to pivot the runtimes from the implicitly on-demand (which can't cache
when using a sandboxed build system like Bazel) to _explicit_ on-demand
runtimes directly with Bazel support.

I've included an example Bazel project that uses this and provides a
bunch of documentation and an example script that should let folks try
this out easily.

---------

Co-authored-by: Geoff Romer <gromer@google.com>
Co-authored-by: David Blaikie <dblaikie@gmail.com>

2026-01-28 02:45:19 +00:00

..

BUILD

Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652)

2026-01-28 02:45:19 +00:00

example.cpp

Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652)

2026-01-28 02:45:19 +00:00

example.h

Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652)

2026-01-28 02:45:19 +00:00

MODULE.bazel

Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652)

2026-01-28 02:45:19 +00:00

update_module_to_nightly.py

Make the Carbon toolchain a viable Bazel module exposing cc_toolchains (#6652)

2026-01-28 02:45:19 +00:00