<div dir="ltr">So the bugfix would be to use the -D parameters, given to cmake-gui,
when configuring a completely new project (=> cache is empty/non
existing)? That would make sense to me and shouldn't be hard to
implement.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 2, 2013 at 1:00 PM, David Cole <span dir="ltr"><<a href="mailto:dlrdave@aol.com" target="_blank">dlrdave@aol.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
-----Original Message-----<br>
From: J Decker <<a href="mailto:d3ck0r@gmail.com" target="_blank">d3ck0r@gmail.com</a>><br>
To: physhh . <<a href="mailto:physhh@gmail.com" target="_blank">physhh@gmail.com</a>><br>
Cc: cmake <<a href="mailto:cmake@cmake.org" target="_blank">cmake@cmake.org</a>><br>
Sent: Fri, Nov 1, 2013 9:51 pm<br>
Subject: Re: [CMake] Forwarding parameters to cmake through cmake-gui<br>
<br>
<br></div><div class="im">
sorry and I should ask; after reading a bit more context;<br>
<br>
why are you using cmake-gui if you have -D's to pass already?<br>
</div></blockquote>
<br>
<br>
It can make sense if you have a script that your users can run that populate a handful of -D options automatically, but that still require users to set some other options via the UI that are hard to determine proper values for automatically.<span class="HOEnZb"><font color="#888888"><br>
<br>
D<br>
<br>
</font></span></blockquote></div><br></div>