1. 12 Sep, 2016 1 commit
    • 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. 08 Jul, 2016 1 commit
  3. 26 Jun, 2016 1 commit
    • Michka Popoff's avatar
      ENH: Do not link against libpython when possible · 772cc086
      Michka Popoff authored
      This is similar to what is already done in ITK and SimpleITK.
      
      The new vtkTargetLinkLibrariesWithDynamicLookup.cmake file is slightly modified copy from ITK (things have been renamed from ITK to VTK). The explanation of what this patch tries to achieve is documented in this file.
      
      A new argument is introduced, called OPTIONAL_PYTHON_LINK. When used, the module will be optionally be linked against libpython. In the module.cmake files, most vtkPython dependencies were moved to COMPILE_DEPENDS, so that libpython is not added to the target_link_libraries() call.
      
      The vtkPython is explicitely linked against the python libraries, as this is a python executable.
      
      Also, the find_package calls for the PythonLibs were made optional when possible.
      
      This fixes the following bug: http://www.vtk.org/Bug/view.php?id=16068
      772cc086
  4. 08 Mar, 2016 1 commit
  5. 25 Aug, 2014 1 commit
    • Utkarsh Ayachit's avatar
      Refactoring CMake code for Python modules. · dc8280bd
      Utkarsh Ayachit authored
      Adding some infrastructure to properly handle vtk-modules that are
      simply Python packages or modules.
      
      This change adds API in vtkModuleMacrosPython to manage all the building
      and installing of Python modules and packages minimizing the confusion.
      
      Past attempts fix six.py, vtk/web etc. failed to distinguish cleanly
      between a Python package and a module which was resulting in directories
      being "unwrapped" on install (e.g. with autobahn) or py files getting
      put in subdirectories (six.py).
      
      This also manages installing on "vtk/web" package under the "vtk"
      package cleanly. For that we needed to move the *.py files in Web/Python
      into a subdirectory reflecting the targetting package structure.
      
      Change-Id: Ic251c34418b07838e5bb483c2b02b12004f17632
      dc8280bd
  6. 28 Jul, 2014 1 commit
    • Ben Boeckel's avatar
      python: install packages properly · 8e8f6477
      Ben Boeckel authored
      With the trailing slash, CMake will merge the directories rather than
      installing the directory as its own entity.
      
      Change-Id: I7b39c0309f27e41476bea43ffd4a624e18b786ed
      8e8f6477
  7. 17 Jun, 2014 1 commit
  8. 05 Sep, 2013 1 commit
  9. 03 Sep, 2013 1 commit
    • David E. DeMarle's avatar
      Make the python module installation directory configurable. · bec28326
      David E. 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
  10. 20 Aug, 2013 1 commit
  11. 19 Aug, 2013 2 commits