> CMake assumes the environment is setup to work. Just like with visual > studio, you have to run vcvars.bat. Basically, cmake expects a working > compiler, and can not modify the PATH. It can not modify the PATH > because it won't be around when make is actually run.
Actually, CMake did an excellent job building stuff without this in my PATH. Once I told CMakeSetup (manually) where the make program was, everything just worked. I presumed it was because you use explicit paths to everything to begin with. So all I needed was some other environmental variable to clue CMakeSetup about where the make program was, and things would be good. Also, I haven't needed vcvars.bat for Visual Studio. I never heard of it until now. I assumed that was because Visual Studio totally messed with my registry and system and CMake already knows how to deal with that. Thanks, Eric _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake