On Nov 11, 2011, at 4:44 PM, Alexander Neundorf wrote: > On Friday 11 November 2011, David Doria wrote: >>> Ok. one more: how exactly did you run cmake ? >>> From the command line or cmake-gui ? >> >> From the CMake-GUI. >> >>> Which generator did you choose ? >>> It should be the "CodeBlocks - NMake Makefiles" one. >> >> I had chosen "CodeBlocks - Unix Makefiles". I just tried again with >> "CodeBlocks - NMake Makefiles", and I get a message box that says: >> "mspdb100.dll is missing". >> >>> This then needs to be run from a terminal which has the VisualStudio >>> environment variables set. >> >> Since I am running the GUI, I'd have to set the "global Windows >> environment variables", right? Which variables do I need to set? > > I think you have to run the GUI from a terminal where the variables are set > up > already. There was usually such an entry in the start menu. I don't know > whether this is also the case with VSExpress. > > Alex > --
That is the best way I have found to run CMake on Windows when multiple Visual Studios are installed. There is a Command Prompt short cut called "Visual Studio Command Prompt" that will have all the compiler paths setup for you. What I do is launch that command prompt then issue "cmake-gui.exe" from there and then CMake will know what compilers I want. Note that there are actually 2 different Visual Studio command prompts: one for 32 bit compiles (Win32) and one for the 64 bit compiles (Win64) Mike Jackson -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
