From d34b377c12d6329e416a941073f151204e9133ca Mon Sep 17 00:00:00 2001
From: Joe Groff <arcata@gmail.com>
Date: Tue, 25 May 2010 20:47:20 -0700
Subject: [PATCH] build-support/factor.cmd: spruce up "unable to detect cl.exe"
 message. use "call" to invoke cl so it doesn't stop the batch job if it's not
 on the path

---
 build-support/factor.cmd | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/build-support/factor.cmd b/build-support/factor.cmd
index da16bceef8..05f1597ace 100644
--- a/build-support/factor.cmd
+++ b/build-support/factor.cmd
@@ -1,10 +1,10 @@
 @echo off
 if not exist Nmakefile goto wrongdir
 
-cl 2>&1 | find "x86" >nul
+call cl 2>&1 | find "x86" >nul
 if not errorlevel 1 goto cl32
 
-cl 2>&1 | find "x64" >nul
+call cl 2>&1 | find "x64" >nul
 if not errorlevel 1 goto cl64
 
 goto nocl
@@ -22,8 +22,9 @@ set _bootimage="boot.winnt-x86.64.image"
 goto platformdefined
 
 :nocl
-echo "Unable to detect cl.exe target platform."
-goto fail
+echo Unable to detect cl.exe target platform.
+echo Make sure you're running within the Visual Studio or Windows SDK environment.
+goto cleanup
 
 :platformdefined