[CMake] Clear cache on upgrade?

[David Cole]

A good rule of thumb is to try just upgrading CMake and running it on
existing build trees. It's obviously quicker than a re-configure from
scratch.

But then, before complaining about something not working, try it in a fresh
build tree first, then if it's still wrong, complain. :-)

It's rare, although it does happen sometimes, that we make a change in
CMake itself that invalidates something that's in an existing cache.

Obviously (or maybe not depending on who you are), some sort of automated
testing, like nightly dashboards, should be doing full re-configures on a
frequent basis anyhow.


HTH,
David


On Mon, Apr 23, 2012 at 2:06 PM, John Drescher <drescherjm at gmail.com> wrote:

> On Mon, Apr 23, 2012 at 1:46 PM, Robert Dailey <rcdailey.lists at gmail.com>
> wrote:
> > I am wondering what a good rule of thumb is when upgrading CMake. Should
> I
> > delete my cache after each upgrade? I'm on Windows.
> > --
>
> I never ever do that on windows. And I have done 100s of builds with
> CMake and many upgrades since CMake 2.4.
>
> John
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120423/355bc3a0/attachment.htm>