1. 28 May, 2018 1 commit
  2. 18 Jan, 2018 1 commit
  3. 17 Jan, 2018 1 commit
  4. 15 Nov, 2017 1 commit
    • Utkarsh Ayachit's avatar
      Make lib build/install dirs match VTKs. · d96b8dde
      Utkarsh Ayachit authored
      We will no longer install libs for ParaView under
      lib/paraview-${version}. ParaView libs are already versioned so we don't
      need to put them under subdirectories.
      This makes it possible to have same logic for locating python packages
      relative to executable in static builds irrespective of build or install
  5. 18 Oct, 2017 1 commit
  6. 30 Jan, 2017 1 commit
  7. 19 Oct, 2016 1 commit
    • Scott Wittenburg's avatar
      Make sure to set PARAVIEW_VERSION · 6d0a952e
      Scott Wittenburg authored
      Since this variable is used to set install library paths for plugins,
      not having it set results in libraries being installed by default to
      a directory named "paraview-".
  8. 17 Oct, 2016 1 commit
  9. 04 Oct, 2016 2 commits
  10. 11 Aug, 2016 1 commit
    • Utkarsh Ayachit's avatar
      Cleanup Qt4/Qt5 cmake files. · 49465100
      Utkarsh Ayachit authored
      Added a new ParaViewQt.cmake that provides new macros to find
      appropriate version of Qt with relevant components. Instead of checking
      which Qt version to use everytime before making Qt macro calls, we now
      use macros in ParaViewQt.cmake.
      Furthermore, we use the VTK module system to pass information about
      which Qt5 version to use (we're not doing the same for Qt4 yet). This
      avoids having any extra crud in ParaViewConfig.cmake or
      UseParaView.cmake to find Qt5 explicitly.
  11. 09 Feb, 2016 1 commit
  12. 24 Apr, 2015 1 commit
  13. 16 May, 2013 1 commit
  14. 14 Mar, 2013 1 commit
    • Utkarsh Ayachit's avatar
      Restructuring CoProcessing/Catalyst modules. · d582543b
      Utkarsh Ayachit authored
      To make it easier to develop adaptors externally, as well as add ability to
      enable/disable Python capabilities in Catalyst, we refactored the CoProcessing
      Two new modules were added vtkPVCatalyst and vtkPVPythonCatalyst. These two
      libraries/module provide the Catalyst components necessary for coprocessing.
      These also provide a C/Fortran API (through CAdaptorAPI/FortranAdaptorAPI or
      the Python enabled CPythonAdaptorAPI/FortranPythonAdaptorAPI headers) that can
      be used within C/Fortran simulation codes.
      Adaptors are now moved to CoProcessing/Adaptors. They have now been updated to
      be able to built outside of ParaView build directory i.e. users can directly
      point CMake to ParaView/CoProcessing/Adaptors/CTHAdaptor as the source directory
      to build the CTH-Adaptor. They will have to point to an existing ParaView build,
      of course, like any other ParaView dependent project.
      ParaView-build builds these adaptors as a separate project (similar to the way
      we build examples). This can be disabled by using the advanced cmake variable
      Also, fix static Python modules initialization. Added a new module in
      Utilities/PythonInitializer which exposes a C function to
      initialize Python modules for static executables. All executables now simply
      link against this one and call the initialization function to init Python.
      Change-Id: Icaacdf8a0d32e03742fbc302008c4ab45c40a22a
  15. 04 Feb, 2013 1 commit
  16. 29 Aug, 2012 1 commit
    • Chris Harris's avatar
      Ensure ParaView_BINARY_DIR is quoted · 3d58f521
      Chris Harris authored
      When appending ParaView_BINARY_DIR to VTK_INCLUDE_DIRS the property
      must be quoted. Build directories with spaces in path will cause issues
  17. 10 Aug, 2012 2 commits
    • Utkarsh Ayachit's avatar
      Fixes to build Examples using an installed version of ParaView. · b1d9be99
      Utkarsh Ayachit authored
      These (along with some pending VTK changes) address issues that pop up when
      building ParaView's Examples with an installed version of ParaView (installed
      using PARAVIEW_INSTALL_DEVELOPMENT_FILES to ON) on Unix machines.
      Change-Id: I8c9fc97da01b7988c55539ec7b8b837a28b0ea4f
    • Utkarsh Ayachit's avatar
      Minor cleanup to ParaViewConfig. · 6b2a4f3b
      Utkarsh Ayachit authored
      Exposing some ParaView options and adding a new variable PARAVIEW_INCLUDE_DIRS
      (same as VTK_INCLUDE_DIRS) just to make it easier for applications.
      Change-Id: I4e0390df2a8761d0f30c4a6a2b6959ca9acd6aaa
  18. 08 Aug, 2012 2 commits
  19. 06 Jul, 2012 2 commits
  20. 26 Aug, 2011 1 commit
  21. 22 Aug, 2011 1 commit
    • Utkarsh Ayachit's avatar
      Fixed BUG #12311. Changed ParaView version number policy. · f744f457
      Utkarsh Ayachit authored
      We now use "git describe" to determine the version for ParaView. Thus we no
      longer have to use minor/major version number trick for releases. "git describe"
      returns a string such as "v3.10.1-1701-g427f2839". The version is then set as
      Major: 3
      Minor: 10
      Patch: 1
      Full : 3.10.1-1701-g427f2839
      If Full=="Major.Minor.Patch", then it's treated as a release.
      Release candidates can be tagged as "x.y.z-rcN" and the version will be set
      If git cannot determine the source version correctly, then
      "CMake/.paraview.version" file is searched for and we try to parse the version
      string from this file. It's a fatal error is both these approaches fail.
  22. 11 Apr, 2011 1 commit
  23. 15 Mar, 2011 1 commit
  24. 05 Mar, 2011 1 commit
  25. 04 Mar, 2011 1 commit
  26. 10 Nov, 2010 1 commit
  27. 29 Oct, 2010 1 commit
  28. 27 Oct, 2010 1 commit
  29. 26 Oct, 2010 1 commit
  30. 12 Apr, 2010 1 commit
  31. 09 Apr, 2010 1 commit
  32. 24 Feb, 2010 1 commit
  33. 23 Feb, 2010 1 commit
  34. 26 Jan, 2010 1 commit
  35. 25 Jan, 2010 1 commit
  36. 13 Jan, 2010 1 commit