GitLab

We no longer need this compatibility layer for the compilers we support.
Use the following commands to switch to standard header and namespace:

 git grep -l vtksys/ios/ | xargs sed -i 's|vtksys/ios/||'
 git grep -l vtksys_ios | xargs sed -i 's|vtksys_ios|std|g'

We no longer need this compatibility layer for the compilers we support.
Use the following commands to switch to standard header and namespace:

 git grep -l vtksys/stl/ | xargs sed -i 's|vtksys/stl/||'
 git grep -l vtksys_stl | xargs sed -i 's|vtksys_stl|std|g'

They're unnecessary and annoying to keep in-sync anyways. Just remove
them.

Change-Id: If7327e0cef17fa1c2d3d41877c4ff7568802fd41

* Added new macros to vtkModuleMacros.cmake to add targets for build-tools. Now
  any component/module creating a tool that's used at compile time should use
  the vtk_compile_tools_target() macro.
* vtk_compile_tools_target(), besides ensuring that the target properties are
  setup properly, adds the target to the VTK_COMPILETOOLS_TARGETS list.
* As a last step, VTK_COMPILETOOLS_TARGETS are exported to both VTKTargets.cmake
  and VTKCompileToolsConfig.cmake.
* When cross compiling VTKCompileToolsConfig.cmake is imported to load
  information about all the build tools.
* vtkCompileTools is a new virtual target that can be used to build host-tools.
  It includes all the targets exported using vtk_compile_tools_target() or
  vtk_compile_tools_target_export() macros.
* For projects, like ParaView, that contain VTK, added a mechanism for the
  parent project to manage importing of the compile tools when cross compiling.

Change-Id: Ibf38868d8ea5f562c7c2682936c72bc11208c5c9

They must export their basic information.

Change-Id: Id3556580d8233b99d34aa06224b7f84c7ad7b584

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>

We take advantage of CMake 2.6 custom-command and target export/import
features to simplify the reference to the vtkHashSource tool.  This also
enables a file-level dependency between vtkSocketCommunicatorHash.h and
the vtkHashSource executable so it will be regenerated when the tool
rebuilds.

These compilers do not seem to upcast references through the ?:
operator.  Instead we use separate simple pointer conversions.

Previously this tool always wrote output to stdout.  Now it will write
to an output file if one is specified on the command line.

This executable needs to run from the build tree and find the vtksys
shared library.  It does not need to be installed.  We can just always
use RPATH to help it find the shared library.

This creates utility executable vtkHashSource to hash source file
content and produce a preprocessor macro defined to the hash value.  It
will be useful to verify matching source during socket handshakes.