[vtk-developers] vtk_common dashboard script

[David Cole]

-----Original Message-----
From: David Cole <dlrdave at aol.com>
To: brad.king <brad.king at kitware.com>; vtk-developers 
<vtk-developers at vtk.org>
Sent: Mon, May 20, 2013 3:32 pm
Subject: Re: [vtk-developers] vtk_common dashboard script


-----Original Message-----
From: Brad King <brad.king at kitware.com>
To: VTK Developers <vtk-developers at vtk.org>
Sent: Mon, May 20, 2013 2:21 pm
Subject: [vtk-developers] vtk_common dashboard script


Hi Folks,

Many of Kitware's VTK dashboard scripts share a "vtk_common.cmake"
script that they include after setting some machine-specific values.
I've published a copy in a "dashboard" branch in the VTK.git repo
(as we've done before in the CMake and ITK repositories) so that
others can use it.

If you maintain a VTK dashboard client please visit this page:

 http://www.vtk.org/Wiki/VTK/Git/Dashboard

and consider switching your client script over to use this helper.

This will simplify the process of updating VTK dashboard client
scripts with changes that need to be applied everywhere.  For
example, the upcoming ExternalData feature will be more efficient
if all dashboard clients add the line

 ExternalData_OBJECT_STORES:STRING=${CTEST_DASHBOARD_ROOT}/ExternalData

to their initial CMakeCache.txt content.  It will store data in a
persistent location outside of any source or build tree so that each
file needs to be downloaded by a client at most once.  The store is
content-addressed so the files are stateless and do not need to be
refreshed each night.  I've updated the vtk_common.cmake script to
do this but many of the current VTK submissions do not use it.

Thanks,
-Brad
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.vtk.org/mailman/listinfo/vtk-developers



Is there any reason not to simply use a reasonable default value for
ExternalData_OBJECT_STORES directly in the VTK CMakeLists file?

Then no dashboard scripts would have to be adjusted. You could just
know that it's in the default location unless otherwise specified.
Perhaps it could be:

(1) parallel to the build tree
(2) under the HOME or USERPROFILE env var directory

get_filename_component and if(EXISTS could be used to place things in a
reasonable default location without any script editing...

Any reason not to do it that way?


Thanks,
David

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.vtk.org/mailman/listinfo/vtk-developers




An added bonus of this technique would be that non-dashboard machines 
would get it automatically, too, without getting multiple copies of it 
under multiple build trees......