These were causing build issues with PGI 14.7

Change-Id: I07f6e61146bd483b12362e5abbbdffc644d2b191

The string only lives as long as its expression, so don't return its
internal c_str.

Change-Id: I32f9fc8ef9847baa645d5743d399b55782122114

Change-Id: I76fea205f42b796bcfc5d47b6f171d39eadd44a4

The main kits are:

    vtkCommon
    vtkFilters
    vtkIO
    vtkImaging
    vtkInteraction
    vtkOpenGL (required due to a dependency cycle from
               vtkRenderingOpenGL on vtkImagingHybrid)
    vtkParallel
    vtkRendering
    vtkViews
    vtkWrapping

Modules which deal with a specialization of another module belong to the
kit related to the specialization (i.e., FiltersParallel and
IOParallelXML both belong to the vtkParallel kit) to avoid circular
dependencies that arise when put into the same kit as the "lesser"
module.

Change-Id: Icae0baa78d62cc0dcce84546541df600d4f311dd

This is split so that vtkIOXML loses its dependency on vtkFiltersAMR
which drags in vtkParallelCore. The parallel-related code can instead be
split out and the core utilities be moved into Common/DataModel.

Change-Id: I621cc40f2afb1831d25e0701a0075ad88dc3e149

It made more sense to have both CAN_PRODUCE_SUB_EXTENT and
CAN_HANDLE_PIECE_REQUEST in vtkAlgorithm.

Change-Id: Ie64bb3e7c8417113bfb7f677c10d8feb5fdddc39

Change-Id: Id76d3bc545a64675a0820cb1d9b45c61a51efc6a

Fixed issued with unigrid enzo datasets. The reader
was calculating number of levels to be 0, which was
leading to a segfault. Added code to detect unigrid
datasets and fixed the issue by setting the number
of levels to 1.

Change-Id: Ie9f1fbe8c3c38c69e5761b357256be9531ed10f3

Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

This patch modifies classes that broke the "rule of three", which
states that classes that declare a destructor must also declare a
copy constructor and assigment operator.

Change-Id: I06b1bb45b493e80e0bae0e8668aa09f494b8056e

A simple implementation of private dependencies, with some of the most
obvious private dependencies moved over. This should be used for all
dependencies that are not exposed in the public API of the classes in
the module.

The target_link_libraries call defaults to private due to the way CMake
implements the link logic. The private dependency logic can help reduce
link line and include directory length for private links where the
dependency's API is not exposed in the module. Also added code to ensure
include directories are not duplicated for modules in the build tree.

Change-Id: If4535338e8d5e9957d7bcce7d3ab0eadec21d2c4

Add to the Testing/Data directory ExternalData content links mirroring
the content and layout we use from the VTKData/Data directory.

Add a CMake/vtkLegacyData.cmake module, included from CMakeLists.txt and
Testing/External/CMakeLists.txt, to call ExternalData_Expand_Arguments
for all data directories added from VTKData/Data.  This will bulk-fetch
all test input data currently used by tests of any module, enabled or
not.  We can make the DATA{} references more granular later.

Add a VTK_TEST_DATA_DIR variable to refer to the directory we tell the
ExternalData module to populate the real data files.  Replace references
to VTK_DATA_ROOT in test command lines (after -D) with references to
VTK_TEST_DATA_DIR.  Drop the VTK_DATA_ROOT CMake option and stop using
the VTKData repository.

Remove the TESTING_DATA option from the vtk_add_test_cxx API and remove
the VTK_DATA_ROOT option from the vtk_add_test_mpi API since all test
input data are now handled through ExternalData and Testing/Data content
links.

Change-Id: Id02490b76ea2e161b9038188264a4830485039d8

Refactor */*/Testing/Cxx/CMakeLists.txt to use the vtk_add_test_cxx
function instead of direct add_test calls.

Change-Id: I73dee627fa87a399c48b409af046b116fc75a0fd

Just added 'static' in front of many private functions.

Change-Id: I892a46d684e00a44e7f84a7343e2cf5690f07eed

The vtkTestingInteractor was trying to run regression tests even if
VTK_DATA_ROOT was not defined.

Many Testing/Cxx CMakeLists.txt files tried to run tests that required
input data, even though VTK_DATA_ROOT was not defined.

Subsequent topics will address Tcl and Python tests.

Change-Id: Iabf242f9f498ce044948ca1d4a29378b76ceb21d

TestFlashReader requires input called: smooth.flash.

According to Yuanxin Liu:
This data set (smooth.flash) is big (1.7G), which is probably why no
one has tried to commit it to VTKData. Unfortunately, as far as I
know, it is the only flash data set that is passed around among the
developers here.  If anyone has a small .flash data set that is good
for testing.  Please post it !

Until a smaller dataset is fouond, remove this test.

Change-Id: I05de065256215f31a7e982ccd7737488ece84ca0

Change-Id: Iaab6fcb6b7e1044f9f22dd3487df598e66e3b239

The remove() command is documented as discouraged and replaced by the
list(REMOVE_ITEM) command which has been around since CMake 2.6.0.

Change-Id: Ibd5a95ef9dc81eb09a28a344ef009d7f1511abf6

Cleaning up the logic in the vtkAMRBaseReader after changes to AMR
datastructures when loading blocks on demand.

Change-Id: Iaed25958b9e005d8982861a1e7b89362674d8e84

- Set spacing and AMRBox separately.
- Expose APIs on vtkAMRInformation on vtkOverlappingAMR
- Add printing and auditing routines for better debugging support
- Fix bug in AMRSliceFilter and add test
- Simplify vtkOverlappingAMR initialization
- change vtkOverlappingAMR:SetGridSpacing to vtkOverlappingAMR:SetSpacing

Change-Id: I4ea8497192bc8c0dcda3a5a3726051342a3d48f5

Change-Id: I8e5cb95599c66188fde686b90e923b18f597281d

Previously, blanking is not generated correctly: if a has a child b
that overlaps it but b is not loaded, a still gets blanked.  The fix
makes sure that a gets blanked only if b is loaded.

Change-Id: Ic0716ee182f946e8e924eab15fe5840297848888

The main motivation for the changes is to improve the efficiency
of AMR data structures by replacing the data set containers and meta
data representation with new data structures.

First, the meta data associated with the AMR data is moved from
vtkInformation to a new class vtkAMRInformation so that they do not
have to be deep copied. Related changes also include:

- Before, when the LOAD_REQUESTED_BLOCKS() key is not set, the reader
  would recompute AMR meta data based on the requested blocks.  This
  is no longer done: meta data always represents what is on file.
  The reason is to avoid the sensitive meta data computation that
  depends on connectivitiy of the requested blocks.

- Processor ranks are no longer stored in the meta data. Filters
  can easily generate them by using
  vtkAMRUtilities::DistributeProcessInformation

- There used to be two types of 1D indices used to reference blocks in
  an AMR: vtkOverlappingAMR::GetFlatIndex and
  vtkOverlappingAMR::GetCompositeIndex. Now only the latter is used.
  The "other" 1D index is file type specific so now only the readers
  reference them (vtkAMRInformation::GetAMRBlockSourceIndex())

- To make it easy to traversal the bounding boxes in the meta data. A
  new key vtkObject::BOUNDING_BOX() has been added that works with
  vtkOverlappingAMRDataIterator. See its use in vtkCompositeCutter for
  an example.

- In a multiprocess setting, vtkAMRSliceFilter for each process computes
  the complete meta data to avoid communication

- Many functions in vtkAMRUtilities are removed because they provide
  support for computing meta data from data sets. In the new design,
  meta information is always created before data sets are constructed.

Second, VtkUniformGridAMR now use a more compact representation of the grid
blocks than the tree implementation done previously. To facilicate
this, vtkCompositeDataSet now becomes a fully abstract class and all
concrete implementation gest pushed to the class vtkDataObjectTree.
In the new implementation, the non-null blocks are stored in an stl
vector. So traversing them (using vtkUniformGridAMRDataIterator) is
efficient.
- The AMRBox has been reduced to store only the lower and upper
  corners.  Information such as origin and spacing are moved to the
  container class vtkAMRInformation, since they are often common to
  all boxes or boxes on the same level.

- File reoganization: - AMR File readers are moved from Filters/AMR to
  IO/AMR - AMR algorithms (vtk*AMR*Algorithm) are moved from
  Filters/General to Common/ExecutionModel

Finally, tkAMRVolumeWrapper is moved from filters to rendering.
The dependency on vtkAMRResampler and vtkParallelCore makes it
difficult for it go to Rendering/Volume so a new module
Rendering/VolumeAMR is created.

Change-Id: Id73d214e6a5ac4d4a08fde5d979365f46edfa390