[Insight-developers] cmake question

[Bill Hoffman]

No, it is still supported, and used for dashboards every night.
Perhaps if you described in more detail exactly what happened we
could figure out if it was a bug in cmake.

As long as the cache edit you make does not cause new cache entries to
appear that are required for the build, an edit, cmake, make should
be enough.    Can you give a reproducible scenario where that does not work?

-Bill
 

At 04:43 PM 3/21/2002 -0700, Joshua Cates wrote:
>Does this mean that the command line interface to cmake is not supported 
>anymore?  It would be nice to have for scripting purposes, at least.
>
>Josh.
>
>______________________________
> Josh Cates                     
> School of Computer Science     
> University of Utah
> Email: cates@cs.utah.edu
> Phone: (801) 587-7697
> URL:   www.cs.utk.edu/~cates
>
>
>On Wed, 20 Mar 2002, Bill Hoffman wrote:
>
>> Manually editing the CMakeCache.txt is discouraged because sometimes it can take
>> several iterations before all values are revealed.   For Unix, it is hoped that
>> users will use the ccmake interface and on windows the CMakeSetup interface should
>> be used.
>> 
>> Another thing you can do, is to type make rebuild_cache, but that should be the
>> same as edition the CMakeCace.txt file and running make.
>> 
>> -Bill
>> 
>> 
>> At 11:12 AM 3/20/2002 -0700, Joshua Cates wrote:
>> >Hello,
>> >
>> >Shouldn't I be able to simply edit CMakeCache.txt entries, rerun cmake and
>> >have the changes reflected?  For some reason this is not working for me
>> >and I have to run cmake -i instead and go through the inquisition. Are
>> >there cmake config files I can clobber before re-running cmake so that it
>> >will force picking up of CMakeCache.txt changes?
>> >
>> >Josh.
>> >
>> >______________________________
>> > Josh Cates                     
>> > School of Computer Science     
>> > University of Utah
>> > Email: cates@cs.utah.edu
>> > Phone: (801) 587-7697
>> > URL:   www.cs.utk.edu/~cates
>> >
>> >
>> >_______________________________________________
>> >Insight-developers mailing list
>> >Insight-developers@public.kitware.com
>> >http://public.kitware.com/mailman/listinfo/insight-developers 
>> 
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers