1. 12 Sep, 2016 29 commits
    • Haocheng LIU's avatar
      Rewrite all public&private dependency in module.cmake file · 6e113ad4
      Haocheng LIU authored
      The current dependency relationship in vtk is unclear and misleading.
      This MR tries to rewrite them based on header files inclusion of headers
      and source files in each module. Corner cases are considered and
      modules are sorted in alphabetical order to facilitate future reference.
      See details in my gitlab python based script project. In future we can continue
      using this script to clean the VTK Dependency easily from
      time to time.
      6e113ad4
  2. 24 Aug, 2016 29 commits
  3. 23 Aug, 2016 29 commits
    • David Gobbi's avatar
      Add cmake check for minimum supported Python version · 643e587e
      David Gobbi authored
      We will be removing support for Python 2.6 and Python 3.2 in the near
      future, so add deprecation warnings for these.  For older versions of
      Python, generate an error.  This deprecation is due in part to the
      fact that WebPython now requires Python 2.7 or 3.3+.
      643e587e
  4. 07 Jul, 2016 29 commits
    • Sean McBride's avatar
      Applied VTK_DELETE_FUNCTION to many constructors · 1853e030
      Sean McBride authored
      vtk(.*)\(const vtk\1&\);\s*//\s*Not implemented[\.]*
      to
      vtk\1(const vtk\1\&) VTK_DELETE_FUNCTION;
      
      vtk(.*)\(const vtk\1 &\);\s*//\s*Not implemented[\.]*
      to
      vtk\1(const vtk\1 \&) VTK_DELETE_FUNCTION;
      
      vtk(.*)\( const vtk\1 & \);\s*//\s*Not implemented[\.]*
      to
      vtk\1( const vtk\1 \& ) VTK_DELETE_FUNCTION;
      
      vtk(.*)\( const vtk\1& \);\s*//\s*Not implemented[\.]*
      to
      vtk\1( const vtk\1\& ) VTK_DELETE_FUNCTION;
      
      vtk(.*) \(const vtk\1&\);\s*//\s*Not implemented[\.]*
      to
      vtk\1 (const vtk\1\&) VTK_DELETE_FUNCTION;
      1853e030
    • Sean McBride's avatar
      Applied VTK_DELETE_FUNCTION for operator= · 2d0e11ef
      Sean McBride authored
      (operator\s*=.*);\s*//\s*Not\s*implemented[\.]*
      to
      \1 VTK_DELETE_FUNCTION;
      
      After that, this finds basically nothing:
      
      operator.*implemented
      
      then manually reverted changed files in VPIC and KWSys folders.
      2d0e11ef
    • Sean McBride's avatar
      include vtkConfigure.h in files that will need it · 37e1de8d
      Sean McBride authored
      These files will eventually need vtkConfigure.h
      for eventual VTK_DELETE_FUNCTION usage.
      37e1de8d
  5. 08 Mar, 2016 29 commits
  6. 07 Mar, 2016 29 commits
  7. 21 Dec, 2015 29 commits
  8. 03 Dec, 2015 29 commits
  9. 01 Dec, 2015 29 commits
    • Mathieu Westphal's avatar
      Adding a NoRelease Option to GilEnsrurer and use it · 7c8572e0
      Mathieu Westphal authored
      Some python calls take care of realeasing gil (eg. Py_Finalize), some when using gilEnsurer before this call, it is needed to only Ensure gil without releasing when going out of scope, has it has already been released. If not python will output a warning.
      So a noRelease parameter have been added to gilEnsurer and this parameter have been used where it was necessary.
      7c8572e0
  10. 27 Nov, 2015 29 commits
  11. 23 Nov, 2015 29 commits
  12. 18 Nov, 2015 29 commits
  13. 12 Nov, 2015 29 commits
    • David Gobbi's avatar
      Remove the toupper macro defined by Python.h. · a4fa4480
      David Gobbi authored
      The Python pyport.h header defines macros for toupper and other
      ctype functions when compiled with __APPLE__ defined.  These macro
      definitions are problematic for C++ in general, and cause compile
      errors with modern compilers.
      a4fa4480
  14. 07 Oct, 2015 29 commits
    • David Gobbi's avatar
      Remove Python version from vtkPythonConfigure.h. · 7d78e329
      David Gobbi authored
      This is no longer needed, and is needlessly restrictive.
      It's best to have a header that can be used by multiple
      versions of python.
      7d78e329
    • Max Smolens's avatar
      Fix HAVE_ROUND-related build warnings in Visual Studio 2013 · 96ca3e6f
      Max Smolens authored
      When built with certain versions of Python, a VTK build with
      VTK_WRAP_PYTHON enabled results in many build warnings. For example:
      
      Python 2.7.10:
      
          c:\python27\include\pyconfig.h(444): warning C4005: 'HAVE_ROUND' : macro redefinition
                    C:\dev\VTK\Utilities\Python\vtkPython.h(77) : see previous definition of 'HAVE_ROUND'
      
      This warning occurs because both vtkPython.h and Python.h define the
      HAVE_ROUND macro, but the definitions don't match. Python 2.7.9+ and
      Python 3.4.2+ define HAVE_ROUND when compiling with Visual Studio 2013+
      (see http://bugs.python.org/issue21958).
      
      Python 3.4.1:
      
          c:\python34\include\pymath.h(22): warning C4273: 'round' : inconsistent dll linkage
                    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\math.h(516) : see previous definition of 'round'
          C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xtgmath.h(206): warning C4273: 'round' : inconsistent dll linkage
                    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\math.h(516) : see previous definition of 'round'
      
      This warning occurs because neither Python.h nor vtkPython.h define HAVE_ROUND.
      
      This commit removes the build warnings by:
      - changing the HAVE_ROUND macro definition to match Python's definition
      - removing the Python version check
      96ca3e6f
  15. 01 Sep, 2015 29 commits
    • Max Smolens's avatar
      Fix HAVE_ROUND-related build warnings in Visual Studio 2013 · 17414afa
      Max Smolens authored
      When built with certain versions of Python, a VTK build with
      VTK_WRAP_PYTHON enabled results in many build warnings. For example:
      
      Python 2.7.10:
      
          c:\python27\include\pyconfig.h(444): warning C4005: 'HAVE_ROUND' : macro redefinition
                    C:\dev\VTK\Utilities\Python\vtkPython.h(77) : see previous definition of 'HAVE_ROUND'
      
      This warning occurs because both vtkPython.h and Python.h define the
      HAVE_ROUND macro, but the definitions don't match. Python 2.7.9+ and
      Python 3.4.2+ define HAVE_ROUND when compiling with Visual Studio 2013+
      (see http://bugs.python.org/issue21958).
      
      Python 3.4.1:
      
          c:\python34\include\pymath.h(22): warning C4273: 'round' : inconsistent dll linkage
                    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\math.h(516) : see previous definition of 'round'
          C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\xtgmath.h(206): warning C4273: 'round' : inconsistent dll linkage
                    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\math.h(516) : see previous definition of 'round'
      
      This warning occurs because neither Python.h nor vtkPython.h define HAVE_ROUND.
      
      This commit removes the build warnings by:
      - changing the HAVE_ROUND macro definition to match Python's definition
      - removing the Python version check
      17414afa
  16. 06 Aug, 2015 29 commits
    • David Gobbi's avatar
      Python API compatibility for py3k. · d3eb4043
      David Gobbi authored
      This is a large change that adds conditional compilation to support
      both python 2 and python 3.  The header vtkPythonCompatibility.h
      does a lot of the necessary work:
      1) PyInt is redefined to PyLong for py3k
      2) PyString is redefied to PyUnicode for py3k
      3) PyBytes is redefined to PyString for python 2
      d3eb4043
  17. 10 Jun, 2015 29 commits
  18. 25 Mar, 2015 29 commits
  19. 18 Dec, 2014 29 commits
  20. 10 Oct, 2014 29 commits
  21. 05 Sep, 2013 29 commits
  22. 03 Sep, 2013 29 commits
    • 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
      bec28326
  23. 16 Aug, 2013 29 commits
  24. 01 Apr, 2013 29 commits
    • David Cole's avatar
      Fix python.h induced Visual Studio compiler warning · 71259985
      David Cole authored
      Python.h defines hypot to be _hypot, which can cause a level 4
      warning coming from math.h with the Visual Studio compiler.
      Use pragma warning to make sure that only level 1 warnings
      may be emitted during the include of Python.h.
      
      Also, remove the custom expression that was trying to suppress
      this warning since it had a missing space in it that prevented
      the match anyhow. It's now unnecessary since the warning is
      not emitted.
      
      Change-Id: Iaf77a0ae76ebab5056fb02d3895e2084168ad731
      71259985
  25. 20 Feb, 2013 29 commits
    • 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
      146e2f78