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>

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

The modular VTK build system completely replaces the old monolithic
CMake code.

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>

Change-Id: Id87b67dff7978ccd3cb19b1cba8971c0edbc9b4f

Change-Id: I949546bf564670fc584d88ab2aeb501d88a8cba2

Change-Id: I0bc8ed0734405e8feac58cd4fb44ca2ef73ce28b

Change-Id: Ie09237bb978dd84e07b4e6e8b0a8109d2dcd8e02

Change-Id: I77a1ae9eb899cdb4433f072db07b9a062f7b2a72

Change-Id: Ife9a64ea03bb54bb14c165bb035c803c82f68aa8

Change-Id: I5a901e547350d185440bb1cb33a4e04f6f18439b

Change-Id: Idd3b58de7a3caeb917fa2834d15371f04783b716

The header states "shouldn't be exposed to users anymore", and so we
should probably look at how we might achieve the same thing with the API
that is intended to be exposed to users. This compiles and works with
Boost 1.49.

Change-Id: I2086f227c45692bd6aa224742369d70f71b5b264

This fixes a number of misspellings in the comments of
the source files in VTK/Infovis. The misspellings were
found using the codespell tool.

Change-Id: Ia6548812e7cb6fe4f455df4ce4f8a3694584076e

In commit 5b9cbfd0 (Fix mpi test executable path for Makefile
generators, 2010-12-21) we replaced use of ${CTEST_CONFIGURATION_TYPE}
with just "." for single-configuration generators.  That leads to paths
ending in "bin/./pvtk" which confuses the Tcl interpreter search path
rendering it unable to load the vtk Tcl package.  TestPProbe-image fails
as a result.

Instead append /${CTEST_CONFIGURATION_TYPE} to the path for multi-config
generators and nothing for single-config generators.

Change-Id: I60d993617f17a5c6a92948040757182aae5a32d7

Change-Id: Ie59ecdd3a52f5e8e57ed71d5b1a21b31e7586b80

Change-Id: Ia74d71ddd9516dd820f400faed2f787220253510

Change-Id: I8bd2a59b601ffbecf7ec72041f9915bd92fde602

Change-Id: I5970870d8d2eb04789f03bb2c13268bf4d241e6e

Change-Id: I673a46e6238bec40feb90ae1666fc667aaa754cc

Change-Id: I1cdd2cd2aa85d917c0432a2fc0ae9e01718507d9

Change-Id: Ib7c95510fbe6beb7b44c6c2db51b74d4090abea9

Change-Id: I2f8cfb3642c695d562cfd14ba28f5f650d2f4355

Change-Id: Ifeb59cefa10e16186cfcba4d0cc0d8246cfbc8b5

This reverts commit f94cb4f8.

On some machines (e.g. Win32-VS91) this test seems to have a leak
related to vtkNew, but on other machines (e.g. linux-g++) the leak
is absent.  This commit is an attempt to investigate the issue.

Change-Id: Ic79a4fac4c3844732ec042900cd867d54c2eac3f

The variable aNode was set but not used.

Change-Id: I35223d37bdc9e251acdf9fe79255e8ddd02809f5

VTK_CREATE use is discouraged, vtkNew gives the same behavior with
concise declaration.

Change-Id: I3f3c369be5dd70942b93f0294e88c7311c388928

This fixes several whitespace issues introduced in this topic, such as
indentation, trailing whitespace.

Change-Id: I5b3cfc1e503fb7ea32fe88627dcb1627ff7da4c4

Change-Id: If99859a706fde9fef8d14ae68f241738ce8c28e4

The dashboards have spoken, ifdefs are needed to acocunt for the change
in API. This should hopefully get everything working again.

Change-Id: I4f1390ccd9f88a734bd1a8f9d72d85954b2b98ed

This fixes bug 12772, where an API change in Boost was causing
compilation failures using Boost 1.38. Thanks to Orion Poplawski for
reporting the issue and posting the patch.

Change-Id: I491b0f1650c0be19319533306eb10597dc96fa06

The dashboards have spoken, ifdefs are needed to acocunt for the change
in API. This should hopefully get everything working again.

Change-Id: I4f1390ccd9f88a734bd1a8f9d72d85954b2b98ed

This fixes bug 12772, where an API change in Boost was causing
compilation failures using Boost 1.38. Thanks to Orion Poplawski for
reporting the issue and posting the patch.

Change-Id: I491b0f1650c0be19319533306eb10597dc96fa06

The vtkstd forwarding headers are deprecated, move to using the STL
headers directly.

Change-Id: Iaeb5ea0c10d40b8e934b6a8ca18f28c3b022b924

Change-Id: Idb9148114c774c4233fa0969b48a17e81ef90010