Searched refs:Ninja (Results 1 – 20 of 20) sorted by relevance
/external/chromium_org/tools/gn/ |
D | README.txt | 1 GN "Generate Ninja" 4 and simpler than GYP. It outputs Ninja build files and optionally GYP files
|
D | escape_unittest.cc | 8 TEST(Escape, Ninja) { in TEST() argument
|
/external/clang/docs/ |
D | HowToSetupToolingForLLVM.rst | 142 (Experimental) Using Ninja Build System 145 Optionally you can use the `Ninja <https://github.com/martine/ninja>`_ 147 Currently this step will require building Ninja from sources. 149 To take advantage of using Clang Tools along with Ninja build you need 152 Clone the Ninja git repository and build Ninja from sources: 169 After doing all of this, you'll need to generate Ninja build files for 177 $ cmake -G Ninja -DCMAKE_EXPORT_COMPILE_COMMANDS=ON path/to/llvm/sources 192 Now you are ready to build and test LLVM using Ninja:
|
D | LibASTMatchersTutorial.rst | 33 Next you need to obtain the CMake build system and Ninja build tool. You 35 aren't built with Ninja support. 60 cmake -G Ninja ../llvm -DLLVM_BUILD_TESTS=ON # Enable tests; default is off. 122 With that done, Ninja will be able to compile our tool. Let's give it
|
D | JSONCompilationDatabase.rst | 33 of compilation databases for Unix Makefile builds (Ninja builds in the
|
/external/clang/runtime/ |
D | CMakeLists.txt | 27 if(CMAKE_GENERATOR MATCHES "Ninja") 29 "Ninja generator can't build compiler-rt as ExternalProject." 30 "Unset LLVM_BUILD_EXTERNAL_COMPILER_RT, or don't use Ninja."
|
/external/chromium_org/third_party/WebKit/Source/bindings/ |
D | BUILD.gn | 53 "--write-file-only-if-changed=1", # Always true for Ninja. FIXME: remove 81 "--write-file-only-if-changed=1", # Always true for Ninja.
|
/external/compiler-rt/lib/tsan/ |
D | check_cmake.sh | 11 …CC=clang CXX=clang++ cmake -G Ninja -DLLVM_ENABLE_WERROR=ON -DCMAKE_BUILD_TYPE=Release -DLLVM_ENAB…
|
/external/chromium_org/third_party/libaddressinput/chromium/cpp/ |
D | README | 21 Ninja: Executes the build files. 32 GYP do not generate the Ninja build files correctly. You can download a
|
/external/llvm/docs/ |
D | HowToCrossCompileLLVM.rst | 19 In this use case, we'll be using CMake and Ninja, on a Debian-based Linux 116 $ cmake -G Ninja <source-dir> <options above> 122 $ CC='clang' CXX='clang++' cmake -G Ninja <source-dir> <options above> 125 Ninja files will be created in the build directory. I strongly suggest
|
/external/chromium_org/tools/gyp/test/win/linker-flags/ |
D | profile.gyp | 7 # Verify that 'Profile' option correctly makes it to LINK steup in Ninja
|
D | program-database.gyp | 8 # step in Ninja.
|
/external/chromium_org/third_party/libaddressinput/src/cpp/ |
D | README | 24 Ninja: Executes the build files. 35 GYP do not generate the Ninja build files correctly. You can download a
|
/external/chromium_org/third_party/WebKit/Source/bindings/scripts/ |
D | scripts.gni | 101 "--write-file-only-if-changed=1", # Always true for Ninja. 161 "--write-file-only-if-changed=1", # Always true for Ninja.
|
/external/skia/docs/ |
D | quickstart.md | 21 3. Create our Ninja build files from our Gyp meta-build files. You only need
|
/external/chromium_org/third_party/skia/docs/ |
D | quickstart.md | 21 3. Create our Ninja build files from our Gyp meta-build files. You only need
|
/external/chromium_org/build/android/ |
D | adb_gdb | 254 \$CHROMIUM_SRC/<out>/Release/lib/ (used by Ninja builds) 255 \$CHROMIUM_SRC/<out>/Debug/lib/ (used by Ninja builds)
|
/external/llvm/cmake/modules/ |
D | HandleLLVMOptions.cmake | 370 # clang doesn't print colored diagnostics when invoked from Ninja 373 CMAKE_GENERATOR STREQUAL "Ninja")
|
/external/icu/icu4c/source/data/locales/ |
D | sr_Latn.txt | 890 "Ninja (885-889)",
|
/external/chromium_org/build/ |
D | common.gypi | 4892 # or compiling with Xcode's Clang. This will allow Ninja builds to 5457 # TODO(justincohen): Ninja only supports simulator for now.
|