Lines Matching +full:libc +full:- +full:build
4 Building and Testing the libc
7 Build modes
10 The libc can be built and tested in two different modes:
12 #. **The overlay mode** - In this mode, one uses the static archive from LLVM's
13 libc along with the system libc. See :ref:`overlay_mode` for more details
14 on building and using the libc in this mode. You can only run the libc
17 .. code-block:: sh
19 $> ninja check-libc
24 #. **The full build mode** - In this mode, the libc is used as the only libc
26 building and using the libc in this mode. Once configured for a full libc
27 build, you can run three kinds of tests:
29 #. Unit tests - You can run unittests by the command:
31 .. code-block:: sh
33 $> ninja check-libc
35 #. Integration tests - You can run integration tests by the command:
37 .. code-block:: sh
39 $> ninja libc-integration-tests
47 .. code-block:: javascript
52 "LLVM_ENABLE_PROJECTS" : "libc",
62 #. To build with Bazel, use the following command:
64 .. code-block:: sh
66 $> bazel build --config=generic_clang @llvm-project//libc/...
70 .. code-block:: sh
72 $> bazel test --config=generic_clang @llvm-project//libc/...
74 #. The bazel target layout of `libc` is located at: `utils/bazel/llvm-project-overlay/libc/BUILD.bazel <https://github.com/llvm/llvm-project/tree/main/utils/bazel/llvm-project-overlay/libc/BUILD.bazel>`_.
81 other than the host's. This can be used to build and test the libc on other
86 As an example, to build and test in a container for 32-bit Arm:
90 .. code-block:: sh
92 $> pacman -S podman qemu-user-static qemu-user-static-binfmt \
93 qemu-system-arm
95 #. To run Bash interactively in an Ubuntu 22.04 container for 32-bit Arm and
96 bind-mount an existing checkout of llvm-project on the host:
98 .. code-block:: sh
100 $> podman run -it \
101 -v </host/path/to/llvm-project>:</container/path/to/llvm-project> \
102 --arch arm docker.io/ubuntu:jammy bash
104 #. Install necessary packages, invoke CMake, build, and run tests.