Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

In other words, changed from the C to the C++ header name.
Did this only in .cxx files, and not in ThirdParty.

Change-Id: I81e2b2c7f2db00e98b37d507232fbc84022e8d8f

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

Change-Id: I7c6ab523d022f28256bb9d29e23ebacbcf6eafdd

Teach vtk_add_test_* to use ExternalData_add_test to add tests and use
DATA{} syntax to reference test baseline images.  Also update direct
add_test calls in several modules.

Change-Id: I1ddcec1c109ea9ca7840be9b6ccf015393039cba

Tell calls to vtk_add_test_(cxx|python|tcl) explicitly when there is no
valid baseline image to avoid passing -V unnecessarily.

Change-Id: Ibe5aecdfa076446ddda0b95e814483eb6622af73

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

Change-Id: I73dee627fa87a399c48b409af046b116fc75a0fd

If VTK_DATA_ROOT is not found, set_tests_properties for some tests
must be blocked.

Change-Id: I8632a1bb30867a7765bf49158ce222d6c2b92eb4

The ASCII file compare failed when the test was run on windows
machines. This patch provides an ASCII compare function that ignores
cr/lf and lf differences. If this new compare function proves useful
it may be include in the Test utilities.

Change-Id: I67c68bcc4d111ac09b94c246d41f45112c566b8f

This test fails on some platforms when the regression and test files
do not match. This patch prints the contents of the two files if they
differ.

Change-Id: Iee6e2c5daffefc654aed405a0585fcf2c71bca1e

Intermittent test failures on SQL tests appear on systems that run
tests in parallel. This patch forces the SQL tests to run serial.

Change-Id: Ie6a8b52c30a73d273ca0188857ca0e541cd4cbc6

Change-Id: If529be09a0d4325b6429c2678055eb4267a07b8e

Berk Geveci authored 12 years ago and Chris Harris committed 12 years ago

The legacy readers and writers somehow ended up in the IO/Geometry
module. I moved them to their own: IO/Legacy. I also cleaned
up dependencies. Some writers somewhat incorrectly subclasses from
the legacy writers even though they supported completely different formats.
They did this to just use things like FileName.

Change-Id: I603753bc7145b317bd71e7798cd2ea8a6c5c56c1

Replace all references to ${VTK_BINARY_DIR}/Testing/Temporary with
${VTK_TEST_OUTPUT_DIR} and set the variable accordingly.  The latter is
shorter and will also be useful to build module tests as an external
application that does not have VTK_BINARY_DIR available.

Change-Id: I5159077c10dd2eab23365e9ac917bc6cbd806589

The URL logic probably needs moving into the relevant modules.

Change-Id: I38df0c41995ee56ed5c9ebed3eb4e8ce4fe757a5

Add a comment to the bottom of each header that used to be excluded from
kit HeaderTesting tests in monolithic VTK.  Format the comment in a way
that cannot be accidentally copied into another header without
modification.  This comment will tell HeaderTesting.py to exclude a
header from testing so we do not have to separately list every excluded
header in every module.

Change-Id: I9d7ae607125459a6527843c8c15ac463a20f6812

VTK Developers authored 12 years ago and Brad King committed 12 years ago

Exclude ThirdParty, Utilities/MetaIO, and Utilities/KWSys as these
are maintained outside VTK.

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>
Co-Author: Brad King <brad.king@kitware.com>

VTK Developers authored 12 years ago and Brad King committed 12 years ago

Include the module-wide header from every header in each module.
Reference the export/visibility macro for the module.

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>

VTK Developers authored 12 years ago and Brad King committed 12 years ago

Add module.cmake, CMakeLists.txt, and other build system files.

The modular VTK build system is not yet mature.  The monolithic build
files had a lot of infrastructure.  The modular build files reproduce
much of the functionality but some features will need to be restored
later.  Document status and tasks in "TODO-Modularization.txt".

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>
Co-Author: Brad King <brad.king@kitware.com>
Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>

VTK Developers authored 12 years ago and Brad King committed 12 years ago

Move source files from their former monolithic VTK location to their new
location in modular VTK without modification.  This preserves enough
information for "git blame -M" and "git log --follow" to connect
modularized VTK files to their original location and history.

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>
Co-Author: Brad King <brad.king@kitware.com>
Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>