authorgravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2026-03-25 01:43:12-07:00
committergravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2026-03-25 01:43:12-07:00
log94355f1920d880837823812481140270d0dc631e
tree13fc86874cf03224ed9fd26ff50746ad1e8f41fd
parent8f6bad065e1661c67520775ffab88e6f135e00f7

README: add information about installation via bootstrap.c

closes #31650

1 files changed, 16 insertions(+), 3 deletions(-)

README.md+16-3
...@@ -87,9 +87,22 @@ therefore lacking these features:...@@ -87,9 +87,22 @@ therefore lacking these features:
87- Ability to compile C, C++, Objective-C, and Objective-C++ files87- Ability to compile C, C++, Objective-C, and Objective-C++ files
8888
89Even when built this way, Zig provides an LLVM backend that produces bitcode89Even when built this way, Zig provides an LLVM backend that produces bitcode
90files, which may be optimized and compiled into object files via a system Clang90files, which may be optimized and compiled into object files via separately
91package. This can be used to produce system packages of Zig applications91installed Clang. Similarly, Zig provides a C backend that produces C source
92without the Zig package dependency on LLVM.92code, which may be optimized and compiled into object files via a separately
93installed C compiler toolchain.
94
95From here you can tinker with `zig2` or you can proceed to installation using
96the build system as usual:
97
98```
99./zig2 build
100```
101
102However, due to the above listed caveats, it is recommended to not proceed to
103this step until this issue is resolved:
104
105[completely eliminate dependency on LLVM library API calls](https://github.com/ziglang/zig/issues/25492)
93106
94## Building from Source Using Prebuilt Zig107## Building from Source Using Prebuilt Zig
95108