Home
last modified time | relevance | path

Searched full:ninja (Results 1 – 25 of 159) sorted by relevance

1234567

/llvm-project/llvm/utils/release/
H A Dbuild_llvm_release.bat81 REM Visual Studio 2019, CMake, Ninja, GNUWin32, SWIG, Python 3,
203 ninja || ninja || ninja || exit /b 1
204 REM ninja check-llvm || ninja check-llvm || ninja check-llvm || exit /b 1
205 REM ninja check-clang || ninja check-clang || ninja chec
[all...]
/llvm-project/clang/docs/
H A DHowToSetupToolingForLLVM.rst62 However, the Ninja generator does support this variable and can be used
66 First, you will need to install `Ninja`_. Once installed, the Ninja
71 will locate the MSVC compiler for the Ninja generator. The `documentation
80 Now you can run CMake with the Ninja generator to export a compilation
85 C:\> mkdir build-ninja
86 C:\> cd build-ninja
87 C:\build-ninja> cmake -G Ninja -DCMAKE_EXPORT_COMPILE_COMMANDS=ON path/to/llvm/sources
90 Ninja build folder. This prevents the two build systems from negatively
93 Once the ``compile_commands.json`` file has been created by Ninja, you can
191 Using Ninja Build System
[all …]
/llvm-project/llvm/utils/
H A Dcheck_ninja_deps.py3 # ======- check-ninja-deps - build debugging script ----*- python -*--========#
11 """Script to find missing formal dependencies in a build.ninja file.
16 dependency graph in build.ninja should have the Tablegen build step as an
18 bug, because depending on the order that ninja chooses to schedule its build
27 This script tries to do that. It's specific to the 'ninja' build tool, because
28 ninja has useful auxiliary output modes that produce the necessary data:
30 - 'ninja -t graph' emits the full DAG of formal dependencies derived from
31 build.ninja (in Graphviz format)
33 - 'ninja -t deps' dumps the database of dependencies discovered at build time
43 - set up a build directory using ninja as the build tool (cmake -G Ninja)
[all …]
/llvm-project/lldb/docs/resources/
H A Dfuzzing.rst24 To build a fuzzer, run the desired ninja command for the fuzzer(s) you want to build:
28 $ ninja lldb-target-fuzzer
29 $ ninja lldb-commandinterpreter-fuzzer
30 $ ninja lldb-expression-fuzzer
42 If you want to run the fuzzers locally, you can run the binaries that were generated with ninja fro…
52 Another way to run the fuzzers is to use a ninja target that will both build the fuzzers and then r…
54 To run the custom ninja targets, run the command for your desired fuzzer:
58 $ ninja fuzz-lldb-target
59 $ ninja fuzz-lldb-commandinterpreter
60 $ ninja fuzz-lldb-expression
[all …]
H A Dbuild.rst28 * `Ninja <https://ninja-build.org>`_ (strongly recommended)
78 $ pkgin install swig python38 cmake ninja-build
79 $ brew install swig cmake ninja
163 build tool for LLVM is Ninja, but other generators like Xcode or Visual Studio
175 $ cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang;lldb" [<cmake options>] path/to/llvm-project/llvm
181 run ninja to perform the actual build.
185 $ ninja lldb lldb-server
188 you can pass just ``lldb``. Ninja will only build what is necessary to run the
193 $ ninja lld
[all...]
/llvm-project/compiler-rt/lib/tsan/
H A Dcheck_cmake.sh11 …CC=clang CXX=clang++ cmake -G Ninja -DLLVM_ENABLE_WERROR=ON -DCMAKE_BUILD_TYPE=Release -DLLVM_ENAB…
13 ninja
14 ninja check-sanitizer
15 ninja check-tsan
16 ninja check-asan
17 ninja check-msan
18 ninja check-lsan
/llvm-project/clang/tools/clang-fuzzer/
H A DDockerfile12 binutils liblzma-dev libz-dev python-all cmake ninja-build subversion \
25 RUN mkdir build0 && cd build0 && cmake -GNinja -DCMAKE_BUILD_TYPE=Release ../llvm && ninja
34 RUN cd build1 && ninja clang-fuzzer
35 RUN cd build1 && ninja clang-objc-fuzzer
36 RUN cd build1 && ninja clang-proto-fuzzer
37 RUN cd build1 && ninja clang-proto-to-cxx
38 RUN cd build1 && ninja clang-loop-proto-to-cxx
39 RUN cd build1 && ninja clang-loop-proto-to-llvm
40 RUN cd build1 && ninja clang-loop-proto-fuzzer
41 RUN cd build1 && ninja clang-llvm-proto-fuzzer
/llvm-project/flang/docs/
H A DGettingStarted.md30 All of the examples below use GCC as the C/C++ compilers and ninja as the build
74 -G Ninja \
88 ninja
104 ninja check-flang
109 ninja install
123 -G Ninja \
138 ninja
139 ninja install
170 -G Ninja \
186 ninja
[all …]
/llvm-project/libcxx/
H A Dappveyor-reqs-install.cmd
/llvm-project/bolt/docs/
H A DOptimizingClang.md50 $ cmake -G Ninja ${TOPLEV}/llvm -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release \
54 $ perf record -e cycles:u -j any,u -- ninja clang
115 $ ninja clean && /bin/time -f %e ninja clang -j48
118 $ ninja clean && /bin/time -f %e ninja clang -j48
133 $ ninja clean && perf stat -e instructions,L1-icache-misses -- ninja clang -j48
143 $ ninja clean && perf stat -e instructions,L1-icache-misses -- ninja clan
[all...]
/llvm-project/libcxx/utils/ci/
H A Drun-buildbot76 # If we can find Ninja/CMake provided by Xcode, use those since we know their
80 if xcrun --find ninja &>/dev/null; then
81 NINJA="$(xcrun --find ninja)"
82 elif which ninja &>/dev/null; then
83 # The current implementation of modules needs the absolute path to the ninja
86 NINJA="$(which ninja)"
88 NINJA="ninja"
[all...]
/llvm-project/.github/workflows/
H A Ddocs.yml116 sudo apt-get install -y cmake ninja-build swig graphviz
125 TZ=UTC ninja -C llvm-build docs-llvm-html docs-llvm-man
134 TZ=UTC ninja -C clang-build docs-clang-html docs-clang-man
143 TZ=UTC ninja -C clang-tools-extra-build docs-clang-tools-html docs-clang-tools-man
152 TZ=UTC ninja -C lldb-build docs-lldb-html docs-lldb-man
161 TZ=UTC ninja -C libunwind-build docs-libunwind-html
170 TZ=UTC ninja -C libcxx-build docs-libcxx-html
179 TZ=UTC ninja -C libc-build docs-libc-html
188 TZ=UTC ninja -C lld-build docs-lld-html
197 TZ=UTC ninja
[all...]
H A Drelease-binaries.yml245 cmake -G Ninja -S llvm -B ${{ steps.setup-stage.outputs.build-prefix }}/build \
255 ninja -v -C ${{ steps.setup-stage.outputs.build-prefix }}/build stage2-package
362 ninja -C ${{ steps.setup-stage.outputs.build-prefix }}/build stage2-check-all
H A Dllvm-project-tests.yml88 - name: Install Ninja
90 uses: llvm/actions/install-ninja@main
133 cmake -G Ninja \
145 ninja -C "$builddir" '${{ inputs.build_target }}'
154 ninja -C "$LLVM_BUILDDIR"
/llvm-project/flang/
H A D.drone.star10 …"apt-get update && apt-get install -y clang-8 cmake ninja-build lld-8 llvm-8-dev libc++-8-dev libc…
14 "ninja install",
18 "ninja -j8",
20 "ninja check-all",
36 "apt-get update && apt-get install -y cmake ninja-build llvm-dev libz-dev git",
40 "ninja install",
44 "ninja -j8",
46 "ninja check-all",
/llvm-project/llvm/docs/
H A DAdvancedBuilds.rst44 $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Release \
48 $ ninja stage2
61 $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Release \
66 $ ninja stage2
98 $ cmake -G Ninja -C <path to source>/clang/cmake/caches/Apple-stage1.cmake <path to source>/llvm
99 $ ninja stage2-distribution
132 $ cmake -G Ninja -C <path to source>/clang/cmake/caches/PGO.cmake \
144 $ cmake -G Ninja -C <path to source>/clang/cmake/caches/PGO.cmake \
161 $ cmake -G Ninja -C <path to source>/clang/cmake/caches/PGO.cmake \
178 $ ninja stage2-instrumented-generate-profdata
[all …]
/llvm-project/libc/src/math/docs/
H A Dadd_math_function.md108 `ninja check-libc`. These exhaustive tests are added and manually run in
151 $ cmake ../llvm -G Ninja \
160 $ ninja libc
165 $ ninja check-libc
170 $ ninja libc-math-smoke-tests
175 $ ninja libc-math-unittests
180 $ ninja libc.test.src.math.<func>_test.__unit__
186 $ ninja libc.test.src.math.exhaustive.<func>_test
192 $ ninja libc.test.src.math.performance_testing.<func>_perf
/llvm-project/llvm/utils/docker/debian10/
H A DDockerfile
/llvm-project/libc/config/windows/
H A DREADME.md21 [Ninja](https://github.com/ninja-build/ninja/releases). (Optional, included
24 crucial as it allows you to use build tools like CMake and Ninja:
62 …cmake -G Ninja ../llvm-project/llvm -DCMAKE_C_COMPILER=C:/src/clang-build/bin/clang-cl.exe -DCMAKE…
86 ninja libc
93 ninja checklibc
/llvm-project/libc/docs/gpu/
H A Dtesting.rst113 $> ninja check-libc
119 $> ninja libc-hermetic-tests
125 $> ninja libc-integration-tests
134 $> ninja check-libc-amdgcn-amd-amdhsa
135 $> ninja check-libc-nvptx64-nvidia-cuda
142 $> ninja -C runtimes/runtimes-amdgcn-amd-amdhsa-bins check-libc
143 $> ninja -C runtimes/runtimes-nvptx64-nvidia-cuda-bins check-libc
144 $> cd runtimes/runtimes-amdgcn-amd-amdhsa-bins && ninja check-libc
145 $> cd runtimes/runtimes-nvptx64-nvidia-cuda-bins && ninja check-libc
/llvm-project/libcxx/docs/
H A DBuildingLibcxx.rst
/llvm-project/libc/docs/
H A Dfull_cross_build.rst63 -G Ninja \
89 $> ninja libc libm
91 The above ``ninja`` command will build the libc static archives ``libc.a`` and
113 -G Ninja \
136 $> ninja libc
138 The above ninja command should build the libc static archives for the target
/llvm-project/libclc/
H A DREADME.TXT
/llvm-project/clang/utils/analyzer/
H A Dentrypoint.py43 ninja()
50 return "build.ninja" not in os.listdir()
54 "cmake -G Ninja -DCMAKE_BUILD_TYPE=Release "
68 def ninja(): function
69 check_call("ninja install", shell=True)
/llvm-project/mlir/utils/clang-tidy/
H A Dapply-clang-tidy.sh41 time ninja -C $BUILD_DIR check-mlir-build-only > ${REJECT_DIR}/ninja.clean.log 2>&1
46 time ninja -C $BUILD_DIR check-mlir-build-only > ${REJECT_DIR}/ninja.clean.log 2>&1
48 echo "check-mlir-build-only failed on clean state! (see ninja.clean.log)"
104 ninja -C $BUILD_DIR check-mlir > ${REJECT_DIR}/ninja.${check}.$(basename $file).log 2>&1
106 echo "check-mlir failed! (see ninja.${check}.${file}.log)"

1234567