authorgravatar for hello@nektro.netMeghan Denny <hello@nektro.net> 2026-03-29 04:32:17+02:00
committergravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2026-04-01 11:41:33+02:00
logda78940dd2175b3f0a60f295f9e3a05cd6bf8f79
tree299721af2ddf0f4608b6fcad55b48dc7c8e805ea
parent27611c10f8dc6a58161699a30a573459d855aede

add a few missing language tags to the README

1 files changed, 13 insertions(+), 13 deletions(-)

README.md+13-13
...@@ -54,7 +54,7 @@ Ensure you have the required dependencies:...@@ -54,7 +54,7 @@ Ensure you have the required dependencies:
5454
55Then it is the standard CMake build process:55Then it is the standard CMake build process:
5656
57```57```sh
58mkdir build58mkdir build
59cd build59cd build
60cmake ..60cmake ..
...@@ -69,7 +69,7 @@ This produces `stage3/bin/zig` which is the Zig compiler built by itself....@@ -69,7 +69,7 @@ This produces `stage3/bin/zig` which is the Zig compiler built by itself.
6969
70In this case, the only system dependency is a C compiler.70In this case, the only system dependency is a C compiler.
7171
72```72```sh
73cc -o bootstrap bootstrap.c73cc -o bootstrap bootstrap.c
74./bootstrap74./bootstrap
75```75```
...@@ -95,7 +95,7 @@ installed C compiler toolchain....@@ -95,7 +95,7 @@ installed C compiler toolchain.
95From here you can tinker with `zig2` or you can proceed to installation using95From here you can tinker with `zig2` or you can proceed to installation using
96the build system as usual:96the build system as usual:
9797
98```98```sh
99./zig2 build99./zig2 build
100```100```
101101
...@@ -118,7 +118,7 @@ The easiest way to obtain both of these artifacts is to use...@@ -118,7 +118,7 @@ The easiest way to obtain both of these artifacts is to use
118directory `out/zig-$target-$cpu` and `out/$target-$cpu`, to be used as118directory `out/zig-$target-$cpu` and `out/$target-$cpu`, to be used as
119`$ZIG_PREFIX` and `$LLVM_PREFIX`, respectively, in the following command:119`$ZIG_PREFIX` and `$LLVM_PREFIX`, respectively, in the following command:
120120
121```121```sh
122"$ZIG_PREFIX/zig" build \122"$ZIG_PREFIX/zig" build \
123 -p stage3 \123 -p stage3 \
124 --search-prefix "$LLVM_PREFIX" \124 --search-prefix "$LLVM_PREFIX" \
...@@ -369,7 +369,7 @@ directory instead of a global installation....@@ -369,7 +369,7 @@ directory instead of a global installation.
369369
370This is the generally recommended approach.370This is the generally recommended approach.
371371
372```372```sh
373cd ~/Downloads373cd ~/Downloads
374git clone --depth 1 --branch release/21.x https://github.com/llvm/llvm-project llvm-project-21374git clone --depth 1 --branch release/21.x https://github.com/llvm/llvm-project llvm-project-21
375cd llvm-project-21375cd llvm-project-21
...@@ -396,7 +396,7 @@ This is occasionally needed when debugging Zig's LLVM backend. Here we build...@@ -396,7 +396,7 @@ This is occasionally needed when debugging Zig's LLVM backend. Here we build
396the three projects separately so that LLVM can be in Debug mode while the396the three projects separately so that LLVM can be in Debug mode while the
397others are in Release mode.397others are in Release mode.
398398
399```399```sh
400cd ~/Downloads400cd ~/Downloads
401git clone --depth 1 --branch release/21.x https://github.com/llvm/llvm-project llvm-project-21401git clone --depth 1 --branch release/21.x https://github.com/llvm/llvm-project llvm-project-21
402cd llvm-project-21402cd llvm-project-21
...@@ -552,7 +552,7 @@ To reduce time spent waiting for the compiler to build, try these techniques:...@@ -552,7 +552,7 @@ To reduce time spent waiting for the compiler to build, try these techniques:
552552
553### Testing553### Testing
554554
555```555```sh
556stage4/bin/zig build test556stage4/bin/zig build test
557```557```
558558
...@@ -572,7 +572,7 @@ Another example is choosing a different set of things to test. For example,...@@ -572,7 +572,7 @@ Another example is choosing a different set of things to test. For example,
572not the other ones. Combining this suggestion with the previous one, you could572not the other ones. Combining this suggestion with the previous one, you could
573do this:573do this:
574574
575```575```sh
576stage4/bin/zig build test-std -Dskip-release576stage4/bin/zig build test-std -Dskip-release
577```577```
578578
...@@ -588,13 +588,13 @@ this information and more in the `zig build --help` menu....@@ -588,13 +588,13 @@ this information and more in the `zig build --help` menu.
588This command will run the standard library tests with only the native target588This command will run the standard library tests with only the native target
589configuration and is estimated to complete in 3 minutes:589configuration and is estimated to complete in 3 minutes:
590590
591```591```sh
592zig build test-std -Dno-matrix592zig build test-std -Dno-matrix
593```593```
594594
595However, one may also use `zig test` directly. From inside the `ziglang/zig` repo root:595However, one may also use `zig test` directly. From inside the `ziglang/zig` repo root:
596596
597```597```sh
598zig test lib/std/std.zig --zig-lib-dir lib598zig test lib/std/std.zig --zig-lib-dir lib
599```599```
600600
...@@ -605,14 +605,14 @@ you're trying to test in practice.)...@@ -605,14 +605,14 @@ you're trying to test in practice.)
605605
606Note that `--test-filter` filters on fully qualified names, so e.g. it's possible to run only the `std.json` tests with:606Note that `--test-filter` filters on fully qualified names, so e.g. it's possible to run only the `std.json` tests with:
607607
608```608```sh
609zig test lib/std/std.zig --zig-lib-dir lib --test-filter "json."609zig test lib/std/std.zig --zig-lib-dir lib --test-filter "json."
610```610```
611611
612If you used `-Dno-lib` and you are in a `build/` subdirectory, you can omit the612If you used `-Dno-lib` and you are in a `build/` subdirectory, you can omit the
613`--zig-lib-dir` argument:613`--zig-lib-dir` argument:
614614
615```615```sh
616stage3/bin/zig test ../lib/std/std.zig616stage3/bin/zig test ../lib/std/std.zig
617```617```
618618
...@@ -771,7 +771,7 @@ To build the LLDB fork, make sure you have...@@ -771,7 +771,7 @@ To build the LLDB fork, make sure you have
771[prerequisites](https://lldb.llvm.org/resources/build.html#preliminaries)771[prerequisites](https://lldb.llvm.org/resources/build.html#preliminaries)
772installed, and then do something like:772installed, and then do something like:
773773
774```774```sh
775$ cmake llvm -G Ninja -B build -DLLVM_ENABLE_PROJECTS="clang;lldb" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DLLVM_ENABLE_ASSERTIONS=ON -DLLDB_ENABLE_LIBEDIT=ON -DLLDB_ENABLE_PYTHON=ON775$ cmake llvm -G Ninja -B build -DLLVM_ENABLE_PROJECTS="clang;lldb" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DLLVM_ENABLE_ASSERTIONS=ON -DLLDB_ENABLE_LIBEDIT=ON -DLLDB_ENABLE_PYTHON=ON
776$ cmake --build build --target lldb --target lldb-server776$ cmake --build build --target lldb --target lldb-server
777```777```