changeset 8940:6cae606d563f

commented out a check for the existence of "cl.exe" for the windows build. The command returns something invalid, so the build fails BECAUSE of this test
author Christian Wirth <christian.wirth@oracle.com>
date Tue, 09 Apr 2013 11:54:28 +0200
parents cdd70fd1479b
children f5aa4361a1fc
files make/windows/create.bat
diffstat 1 files changed, 8 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/make/windows/create.bat	Tue Apr 09 10:48:14 2013 +0200
+++ b/make/windows/create.bat	Tue Apr 09 11:54:28 2013 +0200
@@ -37,10 +37,14 @@
 REM that "grep" be accessible on the PATH. An MKS install does this.
 REM 
 
-cl 2>NUL >NUL
-if %errorlevel% == 0 goto nexttest
-echo Make sure cl.exe is in your PATH before running this script.
-goto end
+
+
+REM (cwirth) does not return a proper error code, so build fails all the time
+REM
+REM cl 2>NUL >NUL
+REM if %errorlevel% == 0 goto nexttest
+REM echo Make sure cl.exe is in your PATH before running this script.
+REM goto end
 
 :nexttest
 grep -V 2>NUL >NUL