nmake

问题 Utility: NMake Platform : Windows 7 I have the following Makefile FILE = $(shell) *.c FILE += $(shell) *.cpp exec: @echo $(FILE) This works perfectly fine with make. This throws up the following error with nmake makefile(2) : fatal error U1036: syntax error : too many names to left of '=' Stop. What could be the reason? Without the line FILE += $(shell) *.cpp nmake works perfectly fine. 回答1: The += syntax is a GNU Make extension that was pioneered in Sun's make in the late 80s. It is not part

问题 I've got a Makefile.mak where I optionally create a test.exe or a DLL from my C-based source code. I'm using CL.EXE and NMAKE. I'd like to modify my CFLAGS macro like this when the target is TEST.EXE: CFLAGS = $(CFLAGS) -DMAIN And, of course, I use this in my C code: #ifdef MAIN ... int main()... yada yada #endif I had tried !IF $@ == "test.exe" but it crashed out and doesn't work logically since the $@, target, isn't deterministic in that part of the makefile. The logical place to define the

问题 Using Windows 7 64x. I've installed Python 3.3.2. I've downloaded MOD_WSGI from http://code.google.com/p/modwsgi/wiki/DownloadTheSoftware?tm=2 I'm now trying to follow this tutorial: http://code.google.com/p/modwsgi/wiki/InstallationOnWindows I run nmake -f win32-ap22py31.mk But I get an error: cl /DWIN32 /DNDEBUG /I"c:\Program Files\Microsoft Visual Studio 9.0\VC\include" /I"c:\Program Files\Microsoft SDKs\Windows\v6.0A\Include" /I"c:\Program Files\Apache Software Foundation\Apache2.2

问题 I face with a problem in linking phase, while working with MSVC9 . It says: NMAKE : fatal error U1095: expanded command line link.exe . . . too long 回答1: lol that sucks but we need more information to answer your question. OS for starters, basically, it is saying that the command line to call the linker is bigger than the buffer allows in cmd.exe itself. If i remember correctly there may be a way to make the command shell utilize a bigger buffer on the command line. Or you can possibly change

问题 I think in nmake if I do this: example : set value=77 echo %%value%% The result will display 77 on the console. Is there a way for me to invoke a .cmd or .bat file that will affect the environment of the nmake.exe process? Suppose I put the statement set value=77 in a file called "setvalue.cmd". Then change the makefile to this: example : setvalue echo %%value%% I get: %value% Alternatively, if there's a way to set a macro within a command block, that would also work. Or, a way to set the

问题 I'm trying to follow the installation instruction for OpenSSL on Windows using this instruction on git bash. On Windows (only pick one of the targets for configuration): $ perl Configure { VC-WIN32 | VC-WIN64A | VC-WIN64I | VC-CE } $ nmake $ nmake test $ nmake install but it failed to recognized nmake. The command resulted in nmake: command not found . Has someone know about nmake? Or am I doing it wrong? 回答1: $ perl Configure { VC-WIN32 | VC-WIN64A | VC-WIN64I | VC-CE } $ nmake but it failed

问题 I am calling cmake -G "NMake Makefiles" from a Microsoft Visual C++ 2010 x64 command prompt. The C compiler identification is correct, but the CXX compiler identification not. I am really confused, because it has worked before, but I could not determine what changed (Windows update?) and raised this issue. So I am searching for the root for this problem. How does CMake find the cxx compiler (on Windows: cl.exe ) and maybe how do I change this behavior? (Setting CMAKE_CXX_COMPILER seems not to

问题 I am calling cmake -G "NMake Makefiles" from a Microsoft Visual C++ 2010 x64 command prompt. The C compiler identification is correct, but the CXX compiler identification not. I am really confused, because it has worked before, but I could not determine what changed (Windows update?) and raised this issue. So I am searching for the root for this problem. How does CMake find the cxx compiler (on Windows: cl.exe ) and maybe how do I change this behavior? (Setting CMAKE_CXX_COMPILER seems not to

问题 I use cmake to generate a NMake file, everything goes fine. I use the x64 toolsets (without Visual Studio, only the SDK), so I type nmake, but it generate a x86 build and not a x64 build. Do you know why ? and how to force nmake to target x64 ? Thanks 回答1: Just to share, use the following to force the x64 platform. Use this command prompt command. VsDevCmd.bat -host_arch=amd64 -arch=amd64 Both -host_arch and -arch are mandatory ! 来源： https://stackoverflow.com/questions/48661598/using-cmake

问题 I use cmake to generate a NMake file, everything goes fine. I use the x64 toolsets (without Visual Studio, only the SDK), so I type nmake, but it generate a x86 build and not a x64 build. Do you know why ? and how to force nmake to target x64 ? Thanks 回答1: Just to share, use the following to force the x64 platform. Use this command prompt command. VsDevCmd.bat -host_arch=amd64 -arch=amd64 Both -host_arch and -arch are mandatory ! 来源： https://stackoverflow.com/questions/48661598/using-cmake