From 94355f1920d880837823812481140270d0dc631e Mon Sep 17 00:00:00 2001 From: Andrew Kelley Date: Wed, 25 Mar 2026 01:43:12 -0700 Subject: [PATCH] README: add information about installation via bootstrap.c closes #31650 --- README.md | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2dea88df211df53b69d13e90961ba4ad3ee1c3a7..a177a5c6f7fabc024f45ed4ec43f36ca176b6e04 100644 --- a/README.md +++ b/README.md @@ -87,9 +87,22 @@ therefore lacking these features: - Ability to compile C, C++, Objective-C, and Objective-C++ files Even when built this way, Zig provides an LLVM backend that produces bitcode -files, which may be optimized and compiled into object files via a system Clang -package. This can be used to produce system packages of Zig applications -without the Zig package dependency on LLVM. +files, which may be optimized and compiled into object files via separately +installed Clang. Similarly, Zig provides a C backend that produces C source +code, which may be optimized and compiled into object files via a separately +installed C compiler toolchain. + +From here you can tinker with `zig2` or you can proceed to installation using +the build system as usual: + +``` +./zig2 build +``` + +However, due to the above listed caveats, it is recommended to not proceed to +this step until this issue is resolved: + +[completely eliminate dependency on LLVM library API calls](https://github.com/ziglang/zig/issues/25492) ## Building from Source Using Prebuilt Zig -- 2.54.0