Lines Matching refs:build

11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
12 does not build the project, it generates the files needed by your build tool
25 The Clang CMake build system supports bootstrap (aka multi-stage) builds. At a
26 high level a multi-stage build is a chain of builds that pass data from one
28 bootstrap build.
30 In a simple two-stage bootstrap build, we build clang using the system compiler,
31 then use that just-built clang to build clang again. In CMake this simplest form
32 of a bootstrap build can be configured with a single option,
54 CMake options starting by ``BOOTSTRAP_`` will be passed only to the stage2 build.
55 This gives the opportunity to use Clang specific build flags.
57 the stage2 build for C and C++.
63 The clang build system refers to builds as stages. A stage1 build is a standard
64 build using the compiler installed on the host, and a stage2 build is built
66 general a stage*n* build is built using the output from stage*n-1*.
72 bootstrapping scenario. Apple Clang is built using a 2-stage build.
75 compiler is a balance of optimization vs build time because it is a throwaway.
79 configuration the Apple Clang build settings are contained in CMake Cache files.
80 You can build an Apple Clang compiler using the following commands:
91 When you build the stage2-distribution target it builds the minimal stage1
97 build configurations.
106 At a high level, the way PGO works is that you build an instrumented compiler,
122 build directory. This takes a really long time because it builds clang twice,
123 and you *must* have compiler-rt in your build tree.
133   <build dir>/tools/clang/stage2-instrumented-bins/utils/perf-training/clang.profdata
135 You can feed that file into the LLVM_PROFDATA_FILE option when you build your
146   llvm-profdata) then uses that compiler to build an instrumented stage2 compiler.
154   compiler with the stage2 profdata to build a PGO-optimized compiler.
176 be a three stage build. The idea of a three stage build is you take your sources
177 and build a compiler (stage1), then use that compiler to rebuild the sources
179 (stage3) with an identical configuration to the stage2 build. At the end of
189   $ cmake --build . --target stage3 --parallel
191 After the build you can compare the stage2 & stage3 compilers.