<div dir="ltr"><div><div><div>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.<br><br></div>I suppose it is a problem in my environment but don't know what to fix.<br>
<br></div>The test you suggest did not fail!<br><br></div><div>Then I tried to configure VTK and cmake-gui from VS command prompt work as expected.<br><br></div><div>May be it is using some information stored in registry?<br>
<br></div><div>Next test is try again cmake-gui from desktop, I hadn't try it until you suggested the test.<br><br></div><div><br></div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/6 Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 8/6/2013 10:03 AM, Jorge Perez wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, cmake work as expected but cmake-gui does not, it does not identify<br>
correctly the C compiler. Both started from de VS command prompt.<br>
<br>
BTW, I didn't expect run cmake-gui from the command prompt.<br>
</blockquote></div>
What did you mean you did not expect run cmake-gui from the command prompt?<br>
<br>
Can you run with --debug-trycompile on a minimal test case:<br>
<br>
project(foo) # only one line needed in the cmake file.<br>
<br>
Then zip up the binary tree and email it to me off the list?<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-Bill<br>
<br>
</font></span></blockquote></div><br></div>