Lines Matching full:build

4 Full Cross Build
16 In this document, we will present recipes to cross build the full libc. When we
17 say *cross build* a full libc, we mean that we will build the full libc for a
22 There are two main recipes to cross build the full libc. Each one serves a
26 * **Standalone cross build** - Using this recipe one can build the libc using a
28   build for the host as well as the target.
29 * **Bootstrap cross build** - In this recipe, one will build the ``clang``
30   compiler and the libc build tools for the host first, and then use them to
31   build the libc for the target. Unlike with the standalone build recipe, the
32   user does not have explicitly build ``clang`` and other build tools.
39 Standalone cross build
43 of user's choice is used to build the libc. The necessary build tools for the
44 host are built first, and those build tools are then used to build the libc for
46 to explicitly build the build tools first and then build the libc. A point to
58   $> mkdir build
59   $> cd build
73 * **Enabled Runtimes** - Since we want to build LLVM-libc, we list
75 * **The full build option** - Since we want to build the full libc, we pass
81 Build step
84 After configuring the build with the above ``cmake`` command, one can build the
91 The above ``ninja`` command will build the libc static archives ``libc.a`` and
95 Bootstrap cross build
107   $> mkdir build
108   $> cd build
129 Build step
132 The build step is similar to the other recipe:
138 The above ninja command should build the libc static archives for the target
144 To build for bare metal, all one has to do is to specify the
146 component of the target triple as ``none``. For example, to build for a
154 To build for a GPU architecture, it should only be necessary to specify the