nmake

When I type the nmake command in the Command Prompt, I am getting this error: 'nmake' is not recognized as an internal or external command operable program or batch file. Also, I couldn't find the nmake.exe file in my system. How to setup the nmake command on Windows? Steve Byrne NMake is part of Microsoft's build tools for building C++ projects. You can get nmake as well as the MSVC++ compiler by downloading Visual C++ Express . Visual C++ Express which runs perfectly fine on Windows 7 . It will install nmake.exe to C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin on Windows 7

I haven't a clue when it comes to building makefiles - I am trying to build luafilesystem in Windows 7 x86 for use with Lua for Windows. I have scoured the internet for tutorials but I just can't figure it out. I got as far as to run NMAKE in the Developer Command Prompt but I received the following error: C:\Users\Me\Desktop\luafilesystem-master\luafilesystem-master>nmake -f Makefile.win Microsoft (R) Program Maintenance Utility Version 12.00.21005.1 Copyright (C) Microsoft Corporation. All rights reserved. cl /c /Fosrc\lfs.obj /MD /O2 /I"c:\lua5.1\include" src\lfs.c Microsoft (R) C/C++

I have both a target test in my Makefile and a directory called test in my project. In GNU Make I can declare it to be phony like this: .PHONY: all compile test clean docs static Is it possible to do the same in NMake? According to http://www.bell-labs.com/project/nmake/tutorial/s6.html , I need to do test: .VIRTUAL but it doesn't work: F:\SomePath>nmake test /f msvc.mk Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. NMAKE : fatal error U1073: don't know how to make '.VIRTUAL' Stop. I think this is what you are looking

I have noticed nmake.exe limits its inference-rule search to one missing file. I find no mention of the problem on the Web. Am I missing something? $ cat Makefile .SUFFIXES: .a .b .d .e all: abc.e .a.b: copy $** $@ .b.d: copy $** $@ .d.e: copy $** $@ $ touch abc.a $ nmake NMAKE : fatal error U1073: don't know how to make 'abc.e' Stop. $ nmake -n abc.a 'abc.a' is up-to-date $ nmake -n abc.b copy abc.a abc.b $ nmake -n abc.d NMAKE : fatal error U1073: don't know how to make 'abc.d' Stop. This same Makefile produces tbe following with GNU make: $ make -n copy abc* abc.b copy abc* abc.d copy abc*

I'm trying to follow steps explained here : but after entering the following into console: configure.exe -release -no-webkit -no-phonon -no-phonon-backend -no-script -no-scripttools -no-qt3support -no-multimedia -no-ltcg I'm getting following error: .... .... .... Running syncqt... Creating qmake... Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cl -c -Fo./ -W3 -nologo -O2 /MP -I. -Igenerators -Igenerators\unix -Igenerators\win32 -Igenerators\mac -Igenerators\symbian -IE:\qt_source\include -IE:\qt_source\include\QtCore

How similar/different are gnu make, microsoft nmake and posix standard make? Obviously there's things like "which OS?", "which compiler?" and "which linker?", but I'm referring specifically to the syntax, semantics and command-line options of the makefiles themselves. If I write makefiles based on manuals for gnu make, what are the most important portability issues that I need to be aware of? GNU Make and POSIX Make share a common core so that GNU Make understands makefiles intended for POSIX Make and interprets them the same way - with very few exceptions. However, many GNU Makefiles use

There seems to be two major conventions for organizing project files and then many variations. Convention 1: High-level type directories, project sub-directories For example, the wxWidgets project uses this style: /solution /bin /prj1 /prj2 /include /prj1 /prj2 /lib /prj1 /prj2 /src /prj1 /prj2 /test /prj1 /prj2 Pros: If there are project dependencies, they can be managed from a single file Flat build file structure Cons: Since test has its own header and cpp files, when you generate the unit test applications for EXE files rather than libraries, they need to include the object files from the

I have a simple C-Programm (1 source file) which I want to compile on Linux and on Windows via make resp. nmake. Is there a possibility to accomplish this with a single makefile? I thought about something like ifeq($(MAKE), nmake) // nmake code here else // make code here endif Unfortunately nmake seems not to understand ifeq , so i cannot use that. I have a working makefile but that produces very ugly results: hello: hello.c $(CC) hello.c That works on both systems. The problem is that the outcome depends on the default behaviors of the respective compilers. Under Linux I get an executeable