1. 14 Nov, 2017 16 commits
    • Utkarsh Ayachit's avatar
      Adding vtkResourceFileLocator · eb1d0948
      Utkarsh Ayachit authored
      vtkResourceFileLocator is a utility class that makes it easier to locate
      resource files in VTK applications.
    • Utkarsh Ayachit's avatar
      Use default library search order to locate syms. · aeb58fd4
      Utkarsh Ayachit authored
      vtkPythonInterpreter failed to locate library for `GetVTKVersion` in
      catalyst examples when using `RTLD_NEXT`. `RTLD_DEFAULT` fixes the
    • Utkarsh Ayachit's avatar
    • Utkarsh Ayachit's avatar
      Fix path setup when in an App on OsX. · 72956ecc
      Utkarsh Ayachit authored
      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.
    • Utkarsh Ayachit's avatar
      Add target for `vtk` python package. · bb2d62df
      Utkarsh Ayachit authored
      This is useful for project that include VTK so that they can add build
      steps after vtk's python package has been built.
    • Utkarsh Ayachit's avatar
      Help Windows builds find PythonD dlls. · 2045916b
      Utkarsh Ayachit authored
    • Utkarsh Ayachit's avatar
      Handle VS generator. · cfc0914e
      Utkarsh Ayachit authored
      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.
    • Utkarsh Ayachit's avatar
    • Utkarsh Ayachit's avatar
      fix VTK module import. · 91422b34
      Utkarsh Ayachit authored
      Use `vtk.${vtk-module}` rather than `${vtk-module}Python` when importing
      VTK modules.
    • Utkarsh Ayachit's avatar
      Help static builds find vtk modules. · e8eece2a
      Utkarsh Ayachit authored
      Fixes to make static builds of VTK locate VTK Python modules correctly.
    • Utkarsh Ayachit's avatar
      Python interpreter fixes. · 78dcea63
      Utkarsh Ayachit authored
      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.
    • Utkarsh Ayachit's avatar
      Clean Python related CMake variables. · b94049f6
      Utkarsh Ayachit authored
      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
      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.
    • Utkarsh Ayachit's avatar
      Cleanup VTK's Python package. · 867d93c2
      Utkarsh Ayachit authored
      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
      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
    • Utkarsh Ayachit's avatar
      Python < 2.4 is no longer supported. Remove related code. · 6dcef46e
      Utkarsh Ayachit authored
      No need to have checks for Python < 2.4.
    • Utkarsh Ayachit's avatar
      Add vtkPythonInterpreter to vtkWrappingPythonCore. · ed0ae846
      Utkarsh Ayachit authored
      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.
    • Utkarsh Ayachit's avatar
      Fix install/build paths for mpi4py. · 3c7c1cef
      Utkarsh Ayachit authored
      Make mpi4py use correct variables for install and build paths for Python
      modules built in VTK.
  2. 13 Nov, 2017 5 commits
  3. 11 Nov, 2017 1 commit
  4. 10 Nov, 2017 13 commits
  5. 09 Nov, 2017 5 commits