The "Generate" button should be enabled after the first configure.<div><br></div><div>It's not enabled because the prevailing theory of the day was that you shouldn't allow generate unless there were *no* *new* cache entries after the most recent configure... -- force users to pay attention to those new red entries -- in other words, it's just history and reluctance to change behavior that's "always been that way"...<div>
<br></div><div>I've always thought that you should be allowed to generate whenever you want to: I'd go so far as to say that "Generate" should be enabled as soon as you open cmake-gui, and that, if there have not been *any* configure steps, it would do the same thing as command line cmake: configure once and generate, all in one click.<br>
<div><br></div><div>Please reply with more feedback:</div><div><br></div><div>How many of you would:</div><div>- keep the current behavior exactly as is, it's good</div><div>- enable "Generate" unconditionally</div>
<div>- something in between</div><div><br></div><div><br></div><div>Thanks,</div><div>David</div><div><br></div><div><br></div><div><div class="gmail_quote">On Mon, Sep 6, 2010 at 12:37 AM, Michael Wild <span dir="ltr"><<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On 5. Sep, 2010, at 20:30 , David Doria wrote:<br>
<br>
> Lately I've been making a class full of students use CMake. Without<br>
> exception, I've had to explain why you have to configure twice to<br>
> build VTK. I imagine they are a representative sample of the "Level 0"<br>
> CMake user - they just want the project they are trying to build "to<br>
> work" with default options, etc.<br>
><br>
> (The explanation is here:<br>
> <a href="http://www.cmake.org/cmake/help/runningcmake.html" target="_blank">http://www.cmake.org/cmake/help/runningcmake.html</a><br>
> under "Why do I have to edit the cache more than once for some projects?"<br>
> if anyone reading this is wondering)<br>
><br>
> Since CMake knows if the cache has changed (it doesn't let you<br>
> generate if it has), when why can't there be a button called "Setup<br>
> project with default options" or "Really configure + generate" that<br>
> configures as many times as necessary and generates all in one step?<br>
> I bet this button would get the most clicks by the general population.<br>
><br>
> Just a suggestion - any thoughts?<br>
><br>
> Thanks,<br>
><br>
> David<br>
<br>
</div>Tell your students to run 'cmake' from the command line (the only sane way of running CMake) and you get the desired behavior. No need to spoil your students with GUIs and such trivia! ;-)<br>
<br>
But honestly, I always wondered at this strangeness, too. Why not configure until CMake can generate? I mean, it still could remember which new cache variables became available and highlight them for the user, but things would be much more intuitive.<br>
<font color="#888888"><br>
Michael<br>
</font><div><div></div><div class="h5"><br>
--<br>
There is always a well-known solution to every human problem -- neat, plausible, and wrong.<br>
H. L. Mencken<br>
<br>
</div></div><br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br></div></div></div>