[Cmake] Pruning cache entries

[Bill Hoffman]

Perhaps the best thing to do, is to move aside the existing file and re-run cmake, then
copy the stuff you need.   Right now cmake does not track the use of variables, I guess
you might be able to write a program like ctest that cleans the cache.  I guess the
the place to start would be adding some tracking of variables used in 
cmSystemTools::GetCacheValue.   It could not be part of the GUI, since the GUI accesses
all the cache values for display anyway.  

-Bill


At 09:23 AM 10/15/2001 -0400, Miller, James V (CRD) wrote:
>Is there any way for CMake to identify cache entries that are not currently being used?
> 
>As a projects needs change or as people determine better ways to set up a project, the CMake cache
>ends up with entries that are no longer being used.
> 
>One option is to wipe the cache and rerun cmake.  But in a project that has a bunch of settings, this can be rather painful. So would it be possible for CMake (or some other executable) to print out a list of the cache entries that are actually used (and more importantly, not used) in generating the makefiles. Then a user could run through the cache and delete the ones that are not needed anymore.
>
>Jim Miller 
>_____________________________________
>Visualization & Computer Vision
>GE Corporate Research & Development
>Bldg. KW, Room C218B
>P.O. Box 8, Schenectady NY 12301
>
>millerjv at crd.ge.com <<mailto:millerjv at crd.ge.com>mailto:millerjv at crd.ge.com>
>(518) 387-4005, Dial Comm: 8*833-4005, 
>Cell: (518) 505-7065, Fax: (518) 387-6981 
>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20011015/79ecad6c/attachment.html>