Shell U1077在live555上运行nmake时出错

Shell U1077在live555上运行nmake时出错,shell,visual-studio-2015,nmake,live555,Shell,Visual Studio 2015,Nmake,Live555,正在尝试为windows构建live555。我按照说明()生成了make文件 运行此命令时: nmake /B -f liveMedia.mak 它的输出是: "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl" -c -Iinclude -I../UsageEnvironment/include -I../groupsock/include -I. -I"C:\Program Files (x86)\Micro

正在尝试为windows构建live555。我按照说明()生成了make文件

运行此命令时:

nmake /B -f liveMedia.mak
它的输出是:

 "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl" -c -Iinclude -I../UsageEnvironment/include -I../groupsock/include    -I. -I"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include" Media.cpp
"C:\Program" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\cl' : return code '0x1'
Stop.
它说“C:\Program”不能被识别为命令

通常它会说,当带空格的路径没有引号时,但是在路径的末尾有引号,我不明白为什么它不能识别它

以下是liveMedia.mak的开头,其中设置了path变量:

INCLUDES = -Iinclude -I../UsageEnvironment/include -I../groupsock/include
PREFIX = /usr/local
LIBDIR = $(PREFIX)/lib
##### Change the following for your environment:
# Comment out the following line to produce Makefiles that generate debuggable code:
NODEBUG=1

# The following definition ensures that we are properly matching
# the WinSock2 library file with the correct header files.
# (will link with "ws2_32.lib" and include "winsock2.h" & "Ws2tcpip.h")
TARGETOS = WINNT

# If for some reason you wish to use WinSock1 instead, uncomment the
# following two definitions.
# (will link with "wsock32.lib" and include "winsock.h")
#TARGETOS = WIN95
#APPVER = 4.0

#!include    <ntwin32.mak>

UI_OPTS =       $(guilflags) $(guilibsdll)
# Use the following to get a console (e.g., for debugging):
CONSOLE_UI_OPTS =       $(conlflags) $(conlibsdll)
CPU=i386

TOOLS32 =       C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC
COMPILE_OPTS =      $(INCLUDES) $(cdebug) $(cflags) $(cvarsdll) -I. -I"$(TOOLS32)\include"
C =         c
C_COMPILER =        "$(TOOLS32)\bin\cl"
C_FLAGS =       $(COMPILE_OPTS)
CPP =           cpp
CPLUSPLUS_COMPILER =    $(C_COMPILER)
CPLUSPLUS_FLAGS =   $(COMPILE_OPTS) 
include=-Iinclude-I../UsageEnvironment/include-I../groupsock/include
前缀=/usr/local
LIBDIR=$(前缀)/lib
#####为您的环境更改以下内容:
#注释掉以下行以生成生成可调试代码的Makefiles:
NODEBUG=1
#以下定义确保我们正确匹配
#具有正确头文件的WinSock2库文件。
#(将链接到“ws2_32.lib”并包括“winsock2.h”和“ws2tcpp.h”)
TARGETOS=WINNT
#如果出于某种原因希望改用WinSock1,请取消注释
#以下是两个定义。
#(将链接到“wsock32.lib”并包括“winsock.h”)
#TARGETOS=WIN95
#APPVER=4.0
#!包括
UI_OPTS=$(guilflags)$(guilibsdll)
#使用以下命令获取控制台(例如,用于调试):
CONSOLE_UI_OPTS=$(conlflags)$(conlibsdll)
CPU=i386
TOOLS32=C:\ProgramFiles(x86)\Microsoft Visual Studio 14.0\VC
COMPILE_OPTS=$(包括)$(cdebug)$(cflags)$(cvarsdll)-I.-I“$(工具32)\include”
C=C
C_编译器=“$(工具32)\bin\cl”
C_标志=$(编译选项)
CPP=CPP
CPLUSPLUS\u编译器=$(C\u编译器)
CPLUSPLUS\u FLAGS=$(编译\u选项)
如果有人看到了错误,或者找到了解决的方法,我会非常感激


提前感谢

尝试dbl引用
工具32=
的路径/prog值?祝你好运。你的意思是:TOOLS32=“C:\ProgramFiles(x86)\Microsoft Visual Studio 14.0\VC”?导致另一个错误的原因错误消息是什么?祝你好运。更糟糕的错误,只是sintax错误或类似的错误,因为它尝试执行“C:\Prog….\VC”\bin\cl”,这不会使sensetry dbl引用
工具32=
的路径/Prog值?祝你好运。你的意思是:TOOLS32=“C:\ProgramFiles(x86)\Microsoft Visual Studio 14.0\VC”?导致另一个错误的原因错误消息是什么?祝你好运。更糟糕的错误,只是sintax错误或类似的错误,因为它尝试执行“C:\Prog….\VC”\bin\cl”,这没有意义