[Insight-developers] modifying BUILDNAME

William A. Hoffman billlist at nycap.rr.com
Thu, 08 Jan 2004 10:06:43 -0500


This is not a ctest/Dart issue.  This problem comes from a change made in cmake 1.8.
In cmake 1.6 BUILDNAME was a cache variable, and in 1.8 it was changed to be a non-cached
variable.    The BUILDNAME variable is still being used, but there is no way to change
it with the CMakeSetup or ccmake.   You can specify it on the command line with a -DBUILDNAME=,
or you can manually edit the cache file, or pre-load the cache. In retrospect, I think 
this change was a mistake.   So, at this point, to fix the problem, I propose the following:


1. Change cmake to cache the variable again.   Put this change into 1.8.4.
 
2. Add the variable as a cache entry in the ITK CMakeLists.txt files, which means
it will start working after an update to ITK, and we won't have to wait for cmake 1.8.4.

3. Lydia, if you want to change this right now, you can add the entry by hand into
the cache, or use a -DBUILDNAME="name" on the command line to CMakeSetup or ccmake.

If I don't hear any other ideas, I willl make the above changes today.
Sorry for the confusion.


-Bill


At 08:44 AM 1/8/2004, Lorensen, William E (Research) wrote:
>"urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word"> 
>I suspect this is related to an unannounced change to cmake/ctest. If Dart is not found, then ctest is used as the client. I think ctest creates the build name auomatically. Make sure Dart is found, then reconfingure and see if that helps,
> 
>Bill
>-----Original Message-----
>From: Lydia Ng [mailto:lng at insightful.com]
>Sent: Thursday, January 08, 2004 8:08 AM
>To: insight-developers at itk.org
>Subject: [Insight-developers] modifying BUILDNAME
>
>Hi,
>
> 
>
>Yesterday on one of my machine I did a new/clean ITK current cvs download and updated CMake to the latest release.
>
>When I ran CMake via the Windows GUI,  I seem to have lost the ability to modify the BUILDNAME.
>
>e.g it uses the generic “Windows-devenv” for the dashboard – while I wanted to mark two different experimental builds differently.
>
>Anyone else have a similar problem?
>
> 
>
>- Lydia