| /netbsd-src/external/apache2/llvm/dist/llvm/utils/release/ |
| H A D | build_llvm_package.bat | 11 REM Visual Studio 2019, CMake, Ninja, GNUWin32, SWIG, Python 3,
72 ninja all || ninja all || ninja all || exit /b
73 ninja check || ninja check || ninja check || exit /b
74 ninja check-clang || ninja check-clang || ninja check-clang || exit /b
75 ninja check-lld || ninja check-lld || ninja check-lld || exit /b
76 ninja check-sanitizer || ninja check-sanitizer || ninja check-sanitizer || exit /b
77 ninja check-clang-tools || ninja check-clang-tools || ninja check-clang-tools || exit /b
78 ninja check-clangd || ninja check-clangd || ninja check-clangd || exit /b
86 ninja all || ninja all || ninja all || exit /b
87 ninja check || ninja check || ninja check || exit /b
[all …]
|
| H A D | test-release.sh | 64 echo " -use-ninja Use ninja instead of make/gmake."
120 -use-ninja )
121 MAKE=ninja
122 generator=Ninja
406 if [ ${MAKE} = 'ninja' ]; then
429 if [ ${MAKE} = 'ninja' ]; then
430 # Ninja doesn't have a documented "keep-going-forever" mode, we need to
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/ |
| H A D | check_ninja_deps.py | 3 # ======- 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 …]
|
| /netbsd-src/external/apache2/llvm/dist/clang/docs/ |
| H A D | HowToSetupToolingForLLVM.rst | 143 Using Ninja Build System
146 Optionally you can use the `Ninja <https://github.com/martine/ninja>`_
148 Currently this step will require building Ninja from sources.
150 To take advantage of using Clang Tools along with Ninja build you need
153 Clone the Ninja git repository and build Ninja from sources:
157 $ git clone git://github.com/martine/ninja.git
158 $ cd ninja/
161 This will result in a single binary ``ninja`` in the current directory.
167 $ sudo cp ninja /usr/local/bin/
168 $ sudo chmod a+rx /usr/local/bin/ninja
[all …]
|
| H A D | LibASTMatchersTutorial.rst | 28 Next you need to obtain the CMake build system and Ninja build tool.
33 git clone https://github.com/martine/ninja.git
34 cd ninja
37 sudo cp ninja /usr/bin/
53 …cmake -G Ninja ../llvm -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_BUILD_TESTS=ON # E…
54 ninja
55 ninja check # Test LLVM only.
56 ninja clang-test # Test Clang only.
57 ninja install
76 Finally, run ninja one last time, and you're done.
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/libcxx/utils/ci/ |
| H A D | run-buildbot | 67 # If we can find Ninja/CMake provided by Xcode, use those since we know their
71 if xcrun --find ninja &>/dev/null; then NINJA="$(xcrun --find ninja)"; else NINJA="ninja"; fi
82 -GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
118 ${NINJA} -vC "${BUILD_DIR}" install-cxx install-cxxabi
121 ${NINJA} -vC "${BUILD_DIR}" check-cxx
124 ${NINJA} -vC "${BUILD_DIR}" check-cxxabi
131 ${NINJA} -vC "${BUILD_DIR}" check-cxx-abilist || (
133 ${NINJA} -vC "${BUILD_DIR}" generate-cxx-abilist
140 ${NINJA} -vC "${BUILD_DIR}" check-cxx-benchmarks
145 ${NINJA} --version
[all …]
|
| /netbsd-src/external/apache2/llvm/dist/clang/tools/clang-fuzzer/ |
| H A D | Dockerfile | 12 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
|
| H A D | README.txt | 36 ninja clang-fuzzer
61 ninja clang-objc-fuzzer
100 ninja clang-proto-fuzzer clang-proto-to-cxx
151 ninja clang-llvm-proto-fuzzer clang-loop-proto-to-llvm
|
| /netbsd-src/sys/external/bsd/compiler_rt/dist/lib/tsan/ |
| H A D | check_cmake.sh | 11 …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
|
| /netbsd-src/external/apache2/llvm/dist/libcxx/ |
| H A D | appveyor-reqs-install.cmd | 38 :: Install Ninja
40 if NOT EXIST ninja (
41 …ppveyor DownloadFile https://github.com/ninja-build/ninja/releases/download/v1.6.0/ninja-win.zip -…
42 7z x ninja.zip -oC:\projects\deps\ninja > nul
43 rm ninja.zip
45 @set PATH=C:\projects\deps\ninja;%PATH%
46 ninja --version
|
| H A D | appveyor.yml | 18 GENERATOR: Ninja
19 MAKE_PROGRAM: ninja
69 - C:\projects\deps\ninja
|
| /netbsd-src/external/apache2/llvm/dist/llvm/bindings/go/ |
| H A D | build.sh | 15 if test -n "`which ninja`" ; then
16 # If Ninja is available, we can speed up the build by building only the
18 (cd $llvm_builddir && cmake -G Ninja $cmake_flags)
19 ninja -C $llvm_builddir llvm-config llvm-go
22 ninja -C $llvm_builddir $llvm_buildtargets FileCheck
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/docker/debian8/ |
| H A D | Dockerfile | 20 # Install a newer ninja release. It seems the older version in the debian repos
22 RUN wget "https://github.com/ninja-build/ninja/releases/download/v1.8.2/ninja-linux.zip" && \
23 echo "d2fea9ff33b3ef353161ed906f260d565ca55b8ca0568fa07b1d2cab90a84a07 ninja-linux.zip" \
25 unzip ninja-linux.zip -d /usr/local/bin && \
26 rm ninja-linux.zip
|
| /netbsd-src/external/apache2/llvm/dist/clang/utils/analyzer/ |
| H A D | entrypoint.py | 41 ninja()
48 return "build.ninja" not in os.listdir()
51 CMAKE_COMMAND = "cmake -G Ninja -DCMAKE_BUILD_TYPE=Release " \
62 def ninja(): function
63 check_call("ninja install", shell=True)
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
| H A D | AdvancedBuilds.rst | 37 $ cmake -G Ninja -DCLANG_ENABLE_BOOTSTRAP=On <path to source>
38 $ ninja stage2
51 …$ cmake -G Ninja -DCLANG_ENABLE_BOOTSTRAP=On -DCLANG_BOOTSTRAP_PASSTHROUGH="CMAKE_INSTALL_PREFIX;C…
52 $ ninja stage2
84 $ cmake -G Ninja -C <path to clang>/cmake/caches/Apple-stage1.cmake <path to source>
85 $ ninja stage2-distribution
118 $ cmake -G Ninja -C <path_to_clang>/cmake/caches/PGO.cmake <source dir>
119 $ ninja stage2-instrumented-generate-profdata
188 $ cmake -G Ninja -C <path_to_clang>/cmake/caches/3-stage.cmake <source dir>
|
| H A D | HowToCrossCompileLLVM.rst | 19 In this use case, we'll be using CMake and Ninja, on a Debian-based Linux
26 * ``ninja-build`` (from backports in Ubuntu)
85 You must set the ``CMAKE_INSTALL_PREFIX``, otherwise a ``ninja install``
146 $ cmake -G Ninja <source-dir> <options above>
152 $ CC='clang' CXX='clang++' cmake -G Ninja <source-dir> <options above>
155 Ninja files will be created in the build directory. I strongly suggest
163 $ ninja
168 You can't run ``ninja check-all`` on this tree because the created
179 $ ninja install
|
| H A D | HowToBuildOnARM.rst | 42 Use Ninja instead of Make: "-G Ninja"
47 After that, just typing ``make -jN`` or ``ninja`` will build everything.
48 ``make -jN check-all`` or ``ninja check-all`` will run all compiler tests. For
|
| /netbsd-src/external/apache2/llvm/dist/libcxx/utils/google-benchmark/ |
| H A D | .gitignore | 38 # ninja generated files.
41 build.ninja
43 rules.ninja
|
| /netbsd-src/external/mit/libuv/dist/.github/workflows/ |
| H A D | sanitizer.yml | 22 sudo apt-get install ninja-build
28 … (cd build-tsan && cmake .. -G Ninja -DBUILD_TESTING=ON -DTSAN=ON -DCMAKE_BUILD_TYPE=Release)
37 (cd build-asan && cmake .. -G Ninja -DBUILD_TESTING=ON -DASAN=ON -DCMAKE_BUILD_TYPE=Debug)
|
| /netbsd-src/external/apache2/llvm/dist/llvm/cmake/modules/ |
| H A D | TableGen.cmake | 11 # Use depfile instead of globbing arbitrary *.td(s) for Ninja.
12 if(CMAKE_GENERATOR STREQUAL "Ninja")
13 # Make output path relative to build.ninja, assuming located on
15 # CMake emits build targets as relative paths but Ninja doesn't identify
16 # absolute path (in *.d) as relative path (in build.ninja)
137 if(NOT CMAKE_GENERATOR STREQUAL "Ninja" AND NOT XCODE)
|
| /netbsd-src/external/apache2/llvm/dist/libcxx/docs/ |
| H A D | BuildingLibcxx.rst | 97 CMake + ninja (MSVC)
100 Building with ninja is required for development to enable tests.
122 > cmake -G Ninja ^
128 > ninja cxx
129 > ninja check-cxx
141 CMake + ninja (MinGW)
146 e.g. the ``mingw-w64-x86_64-clang`` package), together with CMake and ninja.
150 > cmake -G Ninja \
157 > ninja cxx
159 > ninja check-cxx
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/build/ |
| H A D | symlink_or_copy.gni | 10 # https://github.com/ninja-build/ninja/issues/1186
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/secondary/ |
| H A D | BUILD.gn | 48 # executable. This has the effect that `ninja lld` builds lld and then creates
49 # symlinks (via this target), while `ninja bin/lld` only builds lld and doesn't
93 # A pool called "console" in the root BUILD.gn is magic and represents ninja's
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/ |
| H A D | README.rst | 22 creates ninja files, but it can create some IDE projects (MSVC, Xcode, ...)
23 which then shell out to ninja for the actual build.
54 #. ``ninja -C out/gn check-lld`` to build all prerequisites for and run the LLD
61 options. After touching ``out/gn/args.gn`` just run ninja: it will re-invoke gn
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/secondary/clang-tools-extra/test/ |
| H A D | BUILD.gn | 56 # //:default depends on it, so that ninja's default target builds all
96 outputs = [ "$target_gen_dir/run-lit" ] # Non-existing, so that ninja runs it
100 # that it's not part of the default ninja target. Hence, check-clang-tools
|