1. 08 Jan, 2016 1 commit
    • Boris Nagaev's avatar
      Fix CMake error if in directory with ++ in name. · a8495801
      Boris Nagaev authored
      If ${VTK_SOURCE_DIR} contains "++", the following error
      is produced by CMake:
      > RegularExpression::compile(): Nested *?+.
      > RegularExpression::compile(): Error in compile.
      Use STREQUAL instead of MATCHES to compare strings.
  2. 08 Oct, 2015 1 commit
    • David Gobbi's avatar
      Relative import is required for installed VTK. · 25d44596
      David Gobbi authored
      The Python vtk module was failing to import the installed extension
      modules with Python 3, because relative imports now require a leading
      ".".   This problem did not show up on the dashboard, because the
      dash builds run their tests on the build directory (where the vtkpython
      executable has a baked-in PYTHONPATH) but not on the installed programs
      and modules.
      The try/except used in this patch is not an ideal solution, and I would
      rather that the extension modules were placed in Wrapping/Python/vtk/
      during the build, but the required Build/Debug subdirs for Visual Studio
      make that impossible.
  3. 12 Sep, 2015 2 commits
  4. 10 Sep, 2015 1 commit
  5. 24 Aug, 2015 1 commit
  6. 06 Aug, 2015 1 commit
  7. 09 Apr, 2015 1 commit
  8. 11 Mar, 2015 1 commit
    • Scott Wittenburg's avatar
      Fix how we import our argparse fallback implementation. · 566dc51f
      Scott Wittenburg authored
      In environments where Python 2.6 is still in use, there is no
      argparse module included by default.  For these situations, we
      have included our own copy, called _argparse.py, which we usually
      import in the except block in case the default is not present.  At
      some point, the vtk.web package included this file, but at some
      point it was removed and because few sites still use Python 2.6,
      it was not caught.
      This fix puts the _argparse.py in a single location (except for
      where it is needed at build time).  This location is vtk.util,
      and everything now looks there in the fallback case.
      Change-Id: Id64241ffbe4e3cec7e96dae386da1a6385c5f6ed
  9. 10 Mar, 2015 1 commit
  10. 09 Mar, 2015 1 commit
    • Ben Boeckel's avatar
      windows: compile the vtkpython.rc file separately · a701e9c0
      Ben Boeckel authored
      On Windows, if a build tree has a long path, the command line length
      limit can be exceeded. This is normally handled by using response files
      to store the command line arguments rather than passing them directly.
      Unfortunately, CMake does not support this for RC files. To address
      this, compile the rc file separately.
      Change-Id: Ie91e9578c6cf41f7386b914e408c6369c733117f
  11. 09 Feb, 2015 1 commit
  12. 09 Dec, 2014 1 commit
    • Ben Boeckel's avatar
      python: remove echo from custom target · 2b895234
      Ben Boeckel authored
      'echo' is not an executable on Windows and as such is not supported with
      Change-Id: Ie0990d7277d68d2e4cfe051f4cb04c11988dc258
  13. 25 Sep, 2014 1 commit
  14. 07 Jul, 2014 3 commits
  15. 13 Jun, 2014 1 commit
  16. 10 Mar, 2014 1 commit
  17. 03 Sep, 2013 1 commit
    • Dave DeMarle's avatar
      Make the python module installation directory configurable. · bec28326
      Dave DeMarle authored
      Advanced cache variable VTK_INSTALL_PYTHON_MODULE_DIR now controls
      where the install target puts the python .py files and corresponding
      python extension libraries (*Python.so or *Python.dll). ThirdParty
      modules like Zope, Twisted and Autobahn should be placed there,
      vtk extensions should go inside the vtk directory there.
      System installers for instance will likely want to set it to be:
      /usr/local/lib/pythonX.Y/site-packages #Linux
      /Library/Python/X.Y/site-packages #Mac
      C:/PythonXY/Lib/site-packages #Windows
      ParaView will use it to put the VTK python modules underneath its own.
      Also for ParaView's use, there is once again a way to disable installation
      of the vtkpython binary. Now it is done by setting VTK_INSTALL_NO_PYTHON_EXES.
      The change also updates the README.txt per VTK 6.X layout and
      removes references to setup.py, which we no longer support.
      Change-Id: I92c1d65c8ca8aa44ca2d54cc4526bbc72f42eb0d
  18. 16 Aug, 2013 1 commit
  19. 15 Aug, 2013 1 commit
    • Dave DeMarle's avatar
      Use cmake install instead of setup.py to install python wrapping. · beae7c64
      Dave DeMarle authored
      Distutils path is not well maintained and from what packagers
      tell me, largely unused. It is also buggy and hard to use.
      Removing it and letting CMake install instead. Doing this will
      properly remove rpath and likely fix other bugs.
      Change-Id: I60f375449344bcd8b2b2823c248eb69163026a3a
  20. 13 Aug, 2013 1 commit
  21. 08 Jun, 2013 1 commit
    • Dave DeMarle's avatar
      install vtkpython and pvtkpython once again · d8e8502a
      Dave DeMarle authored
      Note, the functionality of vtkpython is pretty broken (as it was in 5.x)
      It can not find your vtk python modules in many cases unless they are
      in a handful of default sytem install locations. In that case you are
      better off just running the normal python interpretter.
      pvtkpython is somewhat more useful in that it adds auto initialization
      and shutdown of MPI.
      Change-Id: I5e42b25bfb34bee104e75d08d2fa15312ee57a31
  22. 26 Mar, 2013 1 commit
  23. 22 Mar, 2013 3 commits
    • Marcus D. Hanwell's avatar
      As discussed in review - rename CLASS->HEADER in modules · 524f23d4
      Marcus D. Hanwell authored
      This (hopefully final commit to this topic) renames the variables to
      HEADER/HEADERS rather than CLASS/CLASSES. The function is also renamed
      from vtk_module_classes_load to vtk_module_headers_load but performs
      essentially the same functions. Updated the documentation to reflect
      these changes.
      Change-Id: I6f44971a865c6788c16c6311f6704f21612a083b
    • Marcus D. Hanwell's avatar
      Complete the rename of vtkWrappingPython · a9b37f20
      Marcus D. Hanwell authored
      The vtkWrappingPython module is now vtkWrappingPythonCore.
      Change-Id: Id3a1f32bc4a21e80181ac45d23ab3457c40d4eae
    • Marcus D. Hanwell's avatar
      Move the Python wrapping to the end · 34903fe1
      Marcus D. Hanwell authored
      This moves the Python wrapping to the end of the build process, using
      the information exported by the module files.
      Change-Id: I711382f79fc1fdb15cd80c87f55dd2f97a2c5cd8
  24. 12 Mar, 2013 1 commit
    • Sean McBride's avatar
      Fix Carbon build with newer Xcodes · 02d783e7
      Sean McBride authored
      We were trying to find Rez in the old hardcoded /Developer
      folder.  Instead, now use OSX_DEVELOPER_ROOT.
      Change-Id: Ie2f337c45f14bb585ccafa78e9a4414a0d17999a
  25. 20 Feb, 2013 1 commit
    • David Gobbi's avatar
      BUG 13875: Add a separate python module to resolve dependencies. · 146e2f78
      David Gobbi authored
      The dependency of Rendering/Matplotlib on Wrapping/Python was causing
      the latter module to be configured too early.  Wrapping/Python must
      be configured after all wrapped modules or it will not be able to capture
      all of the wrapped modules properly.
      The solution is to create a new Python vtk-module that both Wrapping/Python
      and Rendering/Matplotlib can depend on.
      Change-Id: I8348fd80147126866dec91488cb0771a7f412636
  26. 27 Sep, 2012 1 commit
  27. 26 Sep, 2012 1 commit
    • David Gobbi's avatar
      COMP: Allow compilation VTK with custom python on OS X. · 8d1ba85e
      David Gobbi authored
      On OS X, the vtkpython executable was built with "-u _PyMac_Error",
      which assumes that python itself was configured with the option
      "--enable-toolbox-glue".  However, many people who build their own
      OS X python use "--disable-toolbox-glue" to avoid the building of
      Carbon-based OS X extension functions.  The "-u _PyMac_Error" flag
      should only be used with Carbon.
      Change-Id: I61b2754671c9d30c4dbc0b7b95f05dfcb31479db
  28. 22 Sep, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Updating code to use newer CMake MPI variables. · 4e7bdc3d
      Utkarsh Ayachit authored
      FindMPI.cmake has deprecated MPI_LIBRARIES, MPI_INCLUDE_PATH variables (since
      before 2.8.5) and instead exposes MPI_C_LIBRARIES, MPI_C_INCLUDE_PATH variables.
      The old/deprecated variables work very unreliably especially with mpi
      implementation that require multiple libraries e.g. openmpi. Hence updating all
      code to use the newer MPI variables.
      Change-Id: I68e4a72a144e38964111671b0ea6da2314473dbd
  29. 15 Aug, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Fix build issue when VTK_BUILD_ALL_MODULES=ON. · d8e584aa
      Utkarsh Ayachit authored
      In general when Wrapping/Python/CMakeLists.txt gets processed, VTK_WRAP_PYTHON
      is ON and hence vtkPythonWrapping.cmake is automatically included. However, if
      the user didn't turn on VTK_WRAP_PYTHON, but enabled VTK_BUILD_ALL_MODULES, then
      the vtkWrappingPython would be enabled, but CMake would never have imported the
      vtkPythonWrapping.cmake file.
      Hence we ended up with undefined
      vtk_write_python_modules_header_for_wrapped_modules() macro errors. This commit
      fixes that issue.
      Change-Id: I10b7a8e99e48a6a57312dd2a71847f0d19f0d48a
  30. 02 Aug, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Cleanup building of static modules for Python. · dd2c9df0
      Utkarsh Ayachit authored
      This commit lays the ground work to enable building of python modules for static
      VTK builds. This cleans up the code that creates the header file with the list
      of modules to be initialized.
      vtkpython now can be built even when BUILD_SHARED_LIBS is OFF. It statically
      initializes the python wrapped modules.
      Macros to add python modules or generate initialization header file have been
      removed from FindPythonLibs.cmake (and should be deprecated from CMake as well).
      Instead new VTK-specific macros are now added to vtkPythonWrapping.cmake that
      use the information provided by the VTK-modules API to generate the
      initialization header when bulding statically.
      Change-Id: Icca5ccd34397f264dadfe00213501cd4a0eea8b5
  31. 01 Aug, 2012 1 commit
    • Brad King's avatar
      Python: Restore VTK version number to python libraries · 7642e330
      Brad King authored
      The vtk_(add|module)_library macros set the OUTPUT_NAME property of the
      target to add the VTK version number to the library file name.  Since
      commit 1494cdd4 (Add python version numbers only to files, 2012-06-12)
      we set the OUTPUT_NAME property of VTK Python library targets to add the
      python version number, accidentally dropping the VTK version number.
      Add the python version number by getting the OUTPUT_NAME property
      value already set by vtk_add_library and replacing "Python" with
      "Python${XY}".  Then set the OUTPUT_NAME property with the result.
      Change-Id: Ie7ff1268162b077f7bd543df4b785dd49f1be02f
  32. 22 Jun, 2012 1 commit
  33. 15 Jun, 2012 1 commit
    • David Gobbi's avatar
      COMP: Move PythonCore to Python, make it a module again. · 4beb579b
      David Gobbi authored
      In VTK 5.10, the vtkPythonCore library was built in the Wrapping/Python
      directory.  Modularization renamed the library to vtkWrappingPythonCore
      and built it in Wrapping/PythonCore.  Soon afterwards the library was
      named back to vtkPythonCore (its original name), and it became just a
      library (not a modular-style module).
      This patch moves the code back to Wrapping/Python (its original location),
      renames vtkPythonCore to its a new name vtkWrappingPython, and makes the
      library into a modular-style module again.
      Change-Id: Ie41c2bfbe871b085d046e98af9a04a81ed535b37
  34. 14 May, 2012 1 commit
    • Marcus D. Hanwell's avatar
      Use MPI_LIBRARIES instead of the deprecated vars · 5602a806
      Marcus D. Hanwell authored
      The FindMPI module only supports MPI_LIBRARY and MPI_EXTRA_LIBRARY for
      compatibility. The new version of the module actually forces the value
      of MPI_LIBRARY causing issues on some dashboard machines. Migrated to
      use the new MPI_LIBRARIES variable.
      Change-Id: Ieaa663b4e1c748f4902e5b9cfd751fbac4d64c8e
  35. 11 May, 2012 1 commit