GitLab

2fc5c9d3 cmake: use the vtkutf8 module
1a9af1e9 utf8: add module infrastructure
364d9727 Merge branch 'upstream-utf8' into HEAD
b89631f4 utf8 2017-11-14 (4e3d1c17)
a33e1c20 utf8: add an update script
c278559c

 utf8: remove old import
Acked-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !3576

Utkarsh Ayachit authored Nov 15, 2017 and Kitware Robot committed Nov 15, 2017

a423a875 Update vtkPythonInterpreter to use vtkResourceFileLocator.
eb1d0948 Adding vtkResourceFileLocator
aeb58fd4 Use default library search order to locate syms.
6cf0629e Default program name in Python 3 is `python3`.
72956ecc Fix path setup when in an App on OsX.
bb2d62df Add target for `vtk` python package.
2045916b Help Windows builds find PythonD dlls.
cfc0914e

 Handle VS generator.
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ben Boeckel <ben.boeckel@kitware.com>
Merge-request: !3523

Alvaro Sanchez authored Nov 15, 2017 and Kitware Robot committed Nov 15, 2017

6bbbcc42

 Fix various build issues of vtkRenderingOptiX.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Sankhesh Jhaveri <sankhesh.jhaveri@kitware.com>
Merge-request: !3564

Mathieu Westphal authored Nov 15, 2017 and Kitware Robot committed Nov 15, 2017

f53198b3

 Adding opacity support in vtkDiscretizableColorTransferFunction
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Nicolas Vuaille <nicolas.vuaille@kitware.com>
Acked-by: Joachim Pouderoux <joachim.pouderoux@kitware.com>
Merge-request: !3469

Mathieu Westphal authored Nov 15, 2017 and Kitware Robot committed Nov 15, 2017

e5525799

 Fix a bug when opening composite table files
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Nicolas Vuaille <nicolas.vuaille@kitware.com>
Acked-by: Joachim Pouderoux <joachim.pouderoux@kitware.com>
Merge-request: !3574

* upstream-utf8:
  utf8 2017-11-14 (4e3d1c17)

Code extracted from:

    https://gitlab.kitware.com/third-party/utfcpp.git

at commit 4e3d1c175aa11e83852b9cf037d99c0ae0b39ffb (for/vtk).

Will Schroeder authored Nov 15, 2017 and Kitware Robot committed Nov 15, 2017

8baa05ad

 Remove compilation warnings
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3580

vtkResourceFileLocator is a utility class that makes it easier to locate
resource files in VTK applications.

Fix a bug occuring when opening a .vtm with
differents array name. Fixed by reseting the new ColumnArraySelection.

vtkPythonInterpreter failed to locate library for `GetVTKVersion` in
catalyst examples when using `RTLD_NEXT`. `RTLD_DEFAULT` fixes the
issue.

When in an App on OsX, the python packages are under
<app>/Contents/Python. Extend the code to search for `vtk` package to
include this location on OsX.

This is useful for project that include VTK so that they can add build
steps after vtk's python package has been built.

With VS generator, `VTK_BUILD_PYTHON_MODULES_DIR` is build configuration
dependent. Since that dir is not available at configure time, we need to
delay copying of ${module}.py files the the `vtk` Python package to
build time.

Use `vtk.${vtk-module}` rather than `${vtk-module}Python` when importing
VTK modules.

Fixes to make static builds of VTK locate VTK Python modules correctly.

This commit includes various cleanups to Python interpreter
initialization in VTK.

vtkpython/pvtkpython executables now simply use vtkPythonInterpreter.
Previously, the code (which was added before vtkPythonInterpreter was
created) made direct Python API calls. Now, we simply defer to
vtkPythonInterpreter. That makes it possible to have just one
location to setup Python initialization logic in VTK.

Of HPC installations, Python default logic to locate prefix/exec_prefix
relative to the executable name had the potential to fail when using
custom Python builds. The new code tries to setup executable name in the
directory with the Python libraries, if possible.

The code to locate VTK's python modules (both platform dependent and
independent components) has been updated to look for them relative to
the VTK libraries, rather than the executable.

vtkpython now respects `-v` and `-vv` command line arguments to print
debugging information about paths looked up when setting up module
search paths.

This change removes `VTK_INSTALL_PYTHON_MODULE_DIR` and
`VTK_BUILD_PYTHON_MODULE_DIR` cmake variables. These were cache
variabels and they were force set using Python version number the first
time CMake was run. This has the issue of leaving an obsolete value if
Python version was changed in CMake config after the first cmake pass.

Secondly, the two variables complicated module path setup logic since
build and install directory structure for Python modules could
potentially be different.

Simplified this as follows:

`VTK_PYTHON_SITE_PACKAGES_SUFFIX` is a new CMake variable available
for users to set to the "site-packges" suffix to use for build and
install trees. This is non-cache variable and hence we we update it
when Python version is changed in subsequent cmake configurations
without issues (unless explicitly overridden).

The build and install directories for Python modules are set as
`${CMAKE_LIBRARY_OUTPUT_DIRECTORY}/${VTK_PYTHON_SITE_PACKAGES_SUFFIX}`,
`${VTK_INSTALL_LIBRARY_DIR}/${VTK_PYTHON_SITE_PACKAGES_SUFFIX}`
respectively. Thus, we are assured that build and install tree
structures won't differ. `VTK_BUILD_PYTHON_MODULES_DIR` and
`VTK_INSTALL_PYTHON_MODULES_DIR` internal cache variable are available
as shortcuts for these two paths, but we may purge them in future.

VTK's wrapped C++-Python module libraries are built under the
`VTK_BUILD_PYTHON_MODULE_DIR`. That way, we don't need to add extra
paths to locate those. Since those are indeed Python module files,
they should indeed be under the VTK_BUILD_PYTHON_MODULE_DIR.

VTK's Python package is built under the path specified by
`VTK_BUILD_PYTHON_MODULE_DIR` and installed to
`VTK_INSTALL_PYTHON_MODULE_DIR`.

Improved defaults for VTK_BUILD_PYTHON_MODULE_DIR and
VTK_INSTALL_PYTHON_MODULE_DIR. The new defaults avoid having to
separately deal with python module paths for build and install
directories.

No need to have checks for Python < 2.4.

Ensure that vtkPythonInterpreter module is enabled when Python wrapping
is enabled. vtkPythonInterpreter has been upgraded to a core module
required for Python support in VTK.

Make mpi4py use correct variables for install and build paths for Python
modules built in VTK.

Ben Boeckel authored Nov 13, 2017 and Kitware Robot committed Nov 13, 2017

3cdad023

 freerange: remove
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: David Thompson <david.thompson@kitware.com>
Merge-request: !3565

Will Schroeder authored Nov 13, 2017 and Kitware Robot committed Nov 13, 2017

06a14a58 Fixed memory leak
55e9a748 Another regression test image
78af9384 New regression test image
2b65fbb5

 New filter to segment connected point regions.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Merge-request: !3550

Ken Martin authored Nov 13, 2017 and Kitware Robot committed Nov 13, 2017

20576a65

 BUG: Fixing the outlier problem for the Implicite Plane Interaction in VR
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Ken Martin <ken.martin@kitware.com>
Merge-request: !3561

Ken Martin authored Nov 13, 2017 and Kitware Robot committed Nov 13, 2017

ee7301ba

 try speeding up test that can run long
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3567

This commit address the fact that if the outlet is displayed in VR (default behavior) the outlier widget will catch every interaction,
making any interaction with an implicit plane completely impossible.

Contributor: Ken Martin <ken.martin@kitware.com>

Remove mouse events that were not needed

Allison Vacanti authored Nov 10, 2017 and Kitware Robot committed Nov 10, 2017

21da65bd Fix uninitialized variable warning.
3aafec3f

 Use VTK's visibilty settings in VTK-m.
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3555