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