Searched refs:NMake (Results 1 – 19 of 19) sorted by relevance
/external/capstone/ |
D | nmake.bat | 5 cmake -DCMAKE_BUILD_TYPE=Release -G "NMake Makefiles" ..
|
/external/clang/include/clang/Frontend/ |
D | DependencyOutputOptions.h | 19 enum class DependencyOutputFormat { Make, NMake }; enumerator
|
/external/protobuf/cmake/ |
D | README.md | 107 C:\Path\to\protobuf\cmake\build\release>cmake -G "NMake Makefiles" ^ 117 C:\Path\to\protobuf\cmake\build\debug>cmake -G "NMake Makefiles" ^ 286 C:\Path\to\zlib\build\release>cmake -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release ^
|
/external/clang/lib/Frontend/ |
D | DependencyFile.cpp | 366 if (OutputFormat == DependencyOutputFormat::NMake) { in PrintFilename()
|
D | CompilerInvocation.cpp | 866 Opts.OutputFormat = DependencyOutputFormat::NMake; in ParseDependencyOutputArgs()
|
/external/libjpeg-turbo/ |
D | BUILDING.md | 164 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release [additional CMake flags] {source_directory} 273 with NMake, remove `-DCMAKE_BUILD_TYPE=Release` (Debug builds are the default 274 with NMake.) 776 If using NMake:
|
D | CMakeLists.txt | 33 # Debug when using NMake.
|
/external/google-breakpad/src/testing/gtest/cmake/ |
D | internal_utils.cmake | 56 # Newlines inside flags variables break CMake's NMake generator.
|
/external/Reactive-Extensions/RxCpp/ |
D | README.md | 210 cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=RelWithDebInfo -B. ..\CMake
|
/external/libaom/libaom/third_party/googletest/src/googletest/cmake/ |
D | internal_utils.cmake | 56 # Newlines inside flags variables break CMake's NMake generator.
|
/external/googletest/googletest/cmake/ |
D | internal_utils.cmake | 69 # Newlines inside flags variables break CMake's NMake generator.
|
/external/llvm/docs/ |
D | CMake.rst | 137 generator. If you use Visual Studio, "NMake Makefiles" is a generator you can use 138 for building with NMake. By default, CMake chooses the most specific generator
|
/external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
D | CMake.rst | 137 generator. If you use Visual Studio, "NMake Makefiles" is a generator you can use 138 for building with NMake. By default, CMake chooses the most specific generator
|
/external/deqp/external/vulkancts/ |
D | README.md | 34 * Windows: either NMake or Ninja in PATH
|
/external/deqp/external/openglcts/ |
D | README.md | 257 - NMake (must be run in VS or SDK command prompt): "NMake Makefiles"
|
/external/pcre/dist2/doc/html/ |
D | NON-AUTOTOOLS-BUILD.txt | 278 Borland, Msys, MinGW, NMake, and Unix. If possible, use short paths with no
|
/external/pcre/dist2/ |
D | NON-AUTOTOOLS-BUILD | 278 Borland, Msys, MinGW, NMake, and Unix. If possible, use short paths with no
|
/external/clang/docs/ |
D | UsersManual.rst | 599 for NMake or Jom. Ignored unless another option causes Clang to emit a 609 is the convention used by NMake and Jom.
|
/external/clang/include/clang/Driver/ |
D | Options.td | 276 HelpText<"Use NMake/Jom format for the depfile">;
|