<div dir="ltr"><div><div>Wouldn't it then be possible to write a simple shell script for those people who really want that use case which calls cmake with -U and afterwards call cmake-gui?<br></div>Sorry if I didn't understood it as it was ment.<br>
<br><br></div><div>For me the thing is:<br></div><div>I prefer a simple solution which allows the same stuff which is possible with cmake itself (e.g. writing custom scripts which set default entries) and not to bloat the gui with stuff which are not used very often and can be achieved already with a combination of cmake/cmake-gui<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 5, 2013 at 9:40 PM, Matthew Woehlke <span dir="ltr"><<a href="mailto:matthew.woehlke@kitware.com" target="_blank">matthew.woehlke@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2013-11-05 15:14, physhh . wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Tue, Nov 5, 2013 at 8:56 PM, Matthew Woehlke wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 2013-11-05 14:36, Alexander Neundorf wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Once the cache is deleted in cmake-gui, I would expect that the<br>
values from the command line are also forgotten, also the -U<br>
values. Otherwise this cmake would remove the matching entries<br>
from every cache I load.<br>
</blockquote>
<br>
True. (But what if that's what you want?)<br>
</div></blockquote><div class="im">
<br>
Could you give me a use case where u actuall don't want this? As already<br>
stated are the command line parameters the "default" values.<br>
If I dont' want to remove an entry by default I won't pass that parameter.<br>
If I want to remove an entry (but not by default) I will do it with the gui<br>
itself - That's what the gui is for?<br>
</div></blockquote>
<br>
The use case is invoking cmake-gui "by hand" from a command line for a specific project (i.e. specifying the build directory also on the command line).<br>
<br>
As I see it, folks that are used to cmake/ccmake tend to want cmake-gui to work more like that. Whereas folks that are used to doing everything from GUI's and hardly if ever touch a command line want it to work like we're suggesting. Both points of view are IMO valid (though I tend towards greater sympathy for the latter in this case).<br>
<br>
(Personally, I'd say I'm middle of the road; I use a CLI plenty¹ - and TBH, ccmake much more than cmake-gui - but I (try to) understand and respect the non-CLI use case.)<br>
<br>
(¹ ...though not nearly as much as some people I know. I do prefer kwin and kdevelop over ratpoison and vim/emacs, thank you ;-).)<div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
Matthew<br>
<br>
--<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/<u></u>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/<u></u>CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers" target="_blank">http://public.kitware.com/cgi-<u></u>bin/mailman/listinfo/cmake-<u></u>developers</a></div></div></blockquote></div><br></div>