Dean Inglis wrote:
> I ran the VS Express command prompt from the start
> menu folder and checked my env vars which
> appear to have been set by the bat script
> that runs, so all vcvars appear to be correcly
> set. Running cmake (2.4.2 windows exe install)
> from the command prompt still gives a
Brad, Bill,
I ran the VS Express command prompt from the start
menu folder and checked my env vars which
appear to have been set by the bat script
that runs, so all vcvars appear to be correcly
set. Running cmake (2.4.2 windows exe install)
from the command prompt still gives a fail
due to the l
[EMAIL PROTECTED] wrote:
ok, bit of a learning curve here while changing
IDE's (and learining CMake again).
From the CMakeCache.txt for VTK:
MAKECOMMAND:STRING=C:\PROGRA~1\MICROS~2\Common7\IDE\VCExpress.exe VTK.sln
/build Release /project ALL_BUILD
at DOS cmd or cygwin bash prompt the abov
ok, bit of a learning curve here while changing
IDE's (and learining CMake again).
>From the CMakeCache.txt for VTK:
MAKECOMMAND:STRING=C:\PROGRA~1\MICROS~2\Common7\IDE\VCExpress.exe VTK.sln
/build Release /project ALL_BUILD
at DOS cmd or cygwin bash prompt the above
MAKECOMMAND runs.
Dean
Hi,
I searched through the CMake archives
but did not find anything immediately obvious.
I have downloaded the free MS Visual Studio 8
(MS Visual C++ 2005 Express Edition) along
with the MS SDK for Windows 2000. The Cmake
cache shows
//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/PROGRA~1/MICRO
