nmake（NMAKE）.docVIP

nmake（NMAKE） Nmake usage Makefile tutorial nmake command compiler usage I. Introduction We have become accustomed to the powerful IDE provided by Microsoft, and we have rarely considered manual linking projects. The so-called technology is not pressing, and when you are free, you can follow me to understand the command line compiling. C/C++/VC++ programmer or Unix/Linux programming experience should be very familiar with, before I wrote an article describing the use of csc/vbc to carry out the command line, today to introduce MS to provide more efficient and effective compiler tool NMake. Description of MSDN: the Microsoft program maintenance utility (NMAKE.EXE) is a 32 bit tool for generating projects based on commands contained in an instruction file. NMake has rich options for complex compilation operations. It can distinguish between source code changes and selective compilation, which saves you a lot of unnecessary compile time. Two use NMAKE Syntax: NMAKE, [options], [macros], [targets], [@commandfile] Explanation: options is the NMAKE option, macros is the macro definition in the command line, targets is the list of NMAKE target files, and commandfile is the text file (or response file) that contains the command line input. NMAKE uses the Makefile (the generated file, usually the name makefile) that specifies the /F option; if the /F option is not specified, use the Makefile in the current directory. If no Makefile is specified, the NMAKE generates the command line targets using the inference rules. NMake itself is simple, and NMAKE matches the Makefile. Makefile syntax is more complex, usually requires developers to manually write their own Makefile, the next section we explain in detail Makefile. The above options and macros do MSDN links, more content, please consult the relevant page, you can enter here from the NMake MSDN help page, online help here. Writing MAKEFILE Note: the content of this section is from MSDN. Friends who are familiar with this secti