<div dir="ltr"><div class="gmail_quote">On Thu, Aug 28, 2008 at 5:12 AM, Vandenbroucke Sander <span dir="ltr"><<a href="mailto:Sander.Vandenbroucke@vandewiele.com">Sander.Vandenbroucke@vandewiele.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="Ih2E3d">> -----Original Message-----<br>
> From: Bill Hoffman [mailto:<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>]<br>
> Sent: woensdag 27 augustus 2008 14:37<br>
> To: Vandenbroucke Sander<br>
> Cc: <a href="mailto:cmake@cmake.org">cmake@cmake.org</a>; Brad King<br>
> Subject: Re: [CMake] re-config on make all<br>
><br>
> Vandenbroucke Sander wrote:<br>
> > Hi,<br>
> ><br>
> > Sometimes CMake re-configures my build tree when running make.<br>
> > Unfortunately CMake uses wrong options, I normally set those on the<br>
> > command line. This forces me to re-config & rebuild my entire source<br>
> > tree. This is a bit annoying since, in most cases, this is not<br>
necessary<br>
> > and takes a long time.<br>
> ><br>
> > So here is my question: can I prevent the automatic reconfiguration<br>
and<br>
> > throw an error/warning so the user can do a manual reconfig?<br>
> ><br>
><br>
> CMake should use the same options. Your options should have been<br>
stored<br>
> in the cache.<br>
</div>You are right, those options are not cached.<br>
<div class="Ih2E3d"></div></blockquote><div><br></div><div>But Bill's point was that they *should* be cached. So the question is: why are your original command line -D options not saved in CMakeCache.txt...?</div><div>
<br></div><div>What version of CMake are you running?</div><div>(Send output of 'which cmake' and 'cmake --version'...)</div><div><br></div><div>What is your exact original command line for running CMake?</div>
<div><br></div></div></div>