1. 04 Feb, 2020 1 commit
  2. 17 Jan, 2020 2 commits
  3. 16 Jan, 2020 1 commit
  4. 12 Dec, 2019 1 commit
  5. 09 Dec, 2019 1 commit
    • Nicolas Cadart's avatar
      Enable setting system protobuf use for paraview. · 926ebc25
      Nicolas Cadart authored
      Before that, if a system protobuf was found by CMake, the superbuild forced paraview to use it to prevent protobuf runtime version mismatch.
      However, some machines needed to disable using system protobuf as it led to libraries linking errors (especially with pthread).
      
      This patch allows at superbuild level to enable/disable manually using system wide protobuf if found.
      926ebc25
  6. 02 Dec, 2019 1 commit
  7. 27 Nov, 2019 6 commits
  8. 03 Oct, 2019 2 commits
  9. 25 Sep, 2019 1 commit
  10. 12 Aug, 2019 1 commit
  11. 09 Aug, 2019 1 commit
  12. 07 Aug, 2019 1 commit
  13. 25 Jul, 2019 1 commit
  14. 16 Jul, 2019 1 commit
  15. 15 Jul, 2019 1 commit
  16. 12 Jul, 2019 1 commit
  17. 05 Jul, 2019 1 commit
  18. 10 May, 2019 1 commit
  19. 24 Apr, 2019 5 commits
  20. 23 Apr, 2019 3 commits
  21. 15 Apr, 2019 1 commit
  22. 10 Apr, 2019 1 commit
  23. 15 Mar, 2019 1 commit
  24. 25 Feb, 2019 1 commit
  25. 08 Feb, 2019 1 commit
    • Bastien Jacquet's avatar
      Paraview/VTK to use System-wide protobuf · b3d06ffc
      Bastien Jacquet authored
      This avoid run-time error due to the conflict between the VTK-provided
      protobuf 2.6.1 at runtime and system-wide 3.0+ version used by other
      superbuild projects, that make their code require 3.0+ version at runtime
      b3d06ffc
  26. 01 Feb, 2019 2 commits
    • Nick Laurenson's avatar
      Merge branch 'CI/Windows-on-new-SB2' into 'kitware-master' · b0366254
      Nick Laurenson authored
      Add Windows build bot
      
      See merge request bjacquet/VeloView-kwinternal!251
      b0366254
    • Gabriel Devillers's avatar
      Revert "Add ninja for simpler build" · d20e3fa5
      Gabriel Devillers authored
      This reverts commit e762686d3978102c063fbc668704e1f1fd6d2051.
      
      Reasons not to copy ninja.exe to build directory:
      1) it does not make the build much simpler: you still have to install
      git, cmake and Visual Studio. So downloading ninja.exe and adding it to
      your path is not a lot of work (If you are lazy place it in
      C:\Windows\System32). That takes approximately 1 minute.
      2) it does not add ninja.exe to the path, so if you want to rebuild
      only veloview (for a faster build) you go to
      common-superbuild/veloview/build (as indicated by the developer guide),
      and in this directory there is no ninja.exe so your command with
      "ninja" fails and you are perplexed.
      3) it complexifies the work of the CI scripts
      d20e3fa5