| /device/linaro/bootloader/edk2/EdkCompatibilityPkg/Sample/Tools/Source/GenAprioriFile/ |
| GenAprioriFile.c | 377 // incremental builds (that is to say, running nmake a second time
|
| /external/bzip2/ |
| README | 84 nmake -f makefile.msc
|
| /external/googletest/googletest/cmake/ |
| internal_utils.cmake | 63 # Newlines inside flags variables break CMake's NMake generator.
|
| /external/icu/icu4c/source/config/ |
| mh-cygwin-msvc | 224 # These are needed to allow the pkgdata nmake files to work
|
| mh-msys-msvc | 217 # These are needed to allow the pkgdata nmake files to work
|
| /external/libpng/contrib/gregbook/ |
| README | 128 nmake
|
| /external/v8/testing/gtest/cmake/ |
| internal_utils.cmake | 56 # Newlines inside flags variables break CMake's NMake generator.
|
| /external/valgrind/helgrind/tests/ |
| tc20_verifywrap.c | 125 fprintf(stderr, "\nmake pthread_mutex_lock fail: "
|
| /external/wpa_supplicant_8/wpa_supplicant/ |
| nmake.mak | 1 # Makefile for Microsoft nmake to build wpa_supplicant
|
| /external/ImageMagick/ |
| Install-windows.txt | 340 $magick> nmake release
359 $magick> nmake test
|
| /external/swiftshader/third_party/LLVM/docs/ |
| CMake.html | 151 adequate generator. If you use Visual Studio "NMake Makefiles"
152 is a generator you can use for building with NMake. By default,
|
| /external/icu/icu4c/source/data/ |
| makedata.mak | 7 # nmake file for creating data files on win32
9 # nmake /f makedata.mak icumake=$(ProjectDir)
578 # C:\svn\icuproj\icu\trunk\source\data>nmake -f makedata.mak ICUMAKE=C:\svn\icuproj\icu\trunk\source\data\ CFG=x86\Debug uni-core-data
666 # testdata - nmake will invoke pkgdata, which will create testdata.dat
671 nmake /nologo /f "$(TESTDATA)\testdata.mak" TESTDATA=. ICUTOOLS="$(ICUTOOLS)" ICUPBIN="$(ICUPBIN)" ICUP="$(ICUP)" CFG=$(CFGTOOLS) TESTDATAOUT="$(TESTDATAOUT)" TESTDATABLD="$(TESTDATABLD)"
[all...] |
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Tools/freeze/ |
| README | 208 command line C compiler (CL). To compile, run "nmake"; this will
|
| /device/linaro/bootloader/edk2/BaseTools/Source/Python/Common/ |
| DataType.py | 308 TAB_NMAKE = 'Nmake'
|
| /device/linaro/bootloader/edk2/EdkCompatibilityPkg/Sample/Tools/Source/VfrCompile/ |
| VfrServices.cpp | 218 // binary data. This way doing an nmake again will try to build it again, and
|
| /device/linaro/bootloader/edk2/EdkShellPkg/ |
| EdkShellPkg.dsc | 116 # Can not do this in nmake section of edk INF
|
| /external/deqp/external/vulkancts/ |
| README.md | 32 * Windows: either NMake or Ninja in PATH
|
| /external/lzma/CPP/7zip/Bundles/Alone7z/ |
| Alone.dsp | 8 !MESSAGE This is not a valid makefile. To build this project using NMAKE,
11 !MESSAGE NMAKE /f "Alone.mak".
13 !MESSAGE You can specify a configuration when running NMAKE
16 !MESSAGE NMAKE /f "Alone.mak" CFG="Alone - Win32 DebugU"
[all...] |
| /external/protobuf/gtest/ |
| CMakeLists.txt | 66 # Newlines inside flags variables break CMake's NMake generator.
|
| /external/python/cpython2/Tools/freeze/ |
| README | 208 command line C compiler (CL). To compile, run "nmake"; this will
|
| /external/python/cpython3/Tools/freeze/ |
| README | 208 command line C compiler (CL). To compile, run "nmake"; this will
|
| /external/llvm/docs/ |
| 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/libevent/ |
| ChangeLog | [all...] |
| /external/deqp/external/openglcts/ |
| README.md | 252 - NMake (must be run in VS or SDK command prompt): "NMake Makefiles"
[all...] |
| /external/webp/ |
| README | 34 nmake /f Makefile.vc CFG=release-static RTLIBCFG=static OBJDIR=output
438 > nmake /f Makefile.vc CFG=release-static \
|
