[vtk-developers] VTK ExternalData default object store

Bill Lorensen bill.lorensen at gmail.com
Tue May 21 13:59:33 EDT 2013


In SetupForDevelopment.sh we could ask if the developer wants to create an
VTKExternalData directory, parallel to the source tree.

In the CMakeLists.txt for VTK, we could use FindPath to locate the
VTKExternalData directory. If it is not found in the "usual" places, we
could use the default behavior.

Something like;

if (NOT ExternalData_OBJECT_STORES)
  find_path(VTKExternalDataPath NAMES VTKExternalData PATHS
../${VTK_SOURCE} ${HOME})

  if(VTKExternalDataPath)
    set(ExternalData_OBJECT_STORES ${VTKExternalDataPath})
  endif()

endif()


On Tue, May 21, 2013 at 1:44 PM, Brad King <brad.king at kitware.com> wrote:

> On 05/21/2013 01:40 PM, Brad King wrote:
> > My argument is only that default behavior with *no* local configuration
> > should not touch anything outside the source or build tree.
>
> There are already several steps VTK developers run locally:
>
> * Run Utilities/SetupForDevelopment.sh
> * Clone VTKData
> * Run CMake and point VTK_DATA_ROOT at VTKData
>
> We can fold local configuration needed to enable an external default
> into one or more of those steps.  I'm working on a patch to do this
> and will push for review.
>
> -Brad
>



-- 
Unpaid intern in BillsBasement at noware dot com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20130521/f77bd337/attachment.html>


More information about the vtk-developers mailing list