Sorry, I meant that since this situation (windows 8 + visual studio 2010 profesional + SP1) I had always started cmake-gui from the access at desktop.
I suppose it is a problem in my environment but don't know what to fix. The test you suggest did not fail! Then I tried to configure VTK and cmake-gui from VS command prompt work as expected. May be it is using some information stored in registry? Next test is try again cmake-gui from desktop, I hadn't try it until you suggested the test. 2013/8/6 Bill Hoffman <bill.hoff...@kitware.com> > On 8/6/2013 10:03 AM, Jorge Perez wrote: > >> Yes, cmake work as expected but cmake-gui does not, it does not identify >> correctly the C compiler. Both started from de VS command prompt. >> >> BTW, I didn't expect run cmake-gui from the command prompt. >> > What did you mean you did not expect run cmake-gui from the command prompt? > > Can you run with --debug-trycompile on a minimal test case: > > project(foo) # only one line needed in the cmake file. > > Then zip up the binary tree and email it to me off the list? > > > -Bill > >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
