1. 08 Jan, 2020 2 commits
  2. 06 Jan, 2020 1 commit
  3. 11 Dec, 2019 1 commit
  4. 21 Nov, 2019 1 commit
  5. 18 Nov, 2019 1 commit
  6. 07 Nov, 2019 2 commits
  7. 14 Oct, 2019 1 commit
  8. 07 Oct, 2019 1 commit
    • Chuck Atkins's avatar
      llvm: Allow multiple architecture targets · 2c444a07
      Chuck Atkins authored
      Allow a user to pass multiple target architectures for LLVM via the
      llvm_TARGETS_TO_BUILD option now.  Also alow the default configuration to
      map the CMAKE_SYSTEM_PROCESSOR to the appropriate LLVM target.
      2c444a07
  9. 03 Oct, 2019 3 commits
  10. 26 Sep, 2019 1 commit
  11. 22 Sep, 2019 1 commit
    • Utkarsh Ayachit's avatar
      Force legacy OpenGL when mesa is enabled. · ce830d04
      Utkarsh Ayachit authored
      The issue arises when using superbuild (SB) to build binaries with mesa
      enabled on a system that has GLVND-based OpenGL. Mesa that the SB builds
      is without glvnd. Thus, it only builds libGL (old ABI) and not libGLX,
      libOpenGL etc (new GLVND-based ABI).  When building on a system with GLVND,
      ParaView ends up finding and linking directly with the GLVD-based libraries
      i.e. libGLX, libOpenGL etc. However, when building on non-GLVD based system,
      ParaView finds and links using old OpenGL ABI i.e. libGL. Thus, in former
      case the Mesa libGL will never be loaded while in the latter case, it will
      be loaded correctly if found in search path – the mechanism ParaView has
      traditionally relied on for the runtime mesa switching.
      
      In summary, we need to fix how the runtime mesa-dispatch is expected to
      work when using GLVND-based OpenGL interfaces. For 5.7, forcing use of
      legacy OpenGL interfaces when mesa is enabled (as done in attached
      patch), should suffice.
      
      ref:
      https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/
      ce830d04
  12. 20 Sep, 2019 1 commit
  13. 04 Sep, 2019 2 commits
  14. 03 Sep, 2019 2 commits
  15. 16 Aug, 2019 2 commits
  16. 14 Aug, 2019 1 commit
  17. 07 Aug, 2019 8 commits
  18. 05 Aug, 2019 5 commits
  19. 03 Aug, 2019 1 commit
  20. 02 Aug, 2019 2 commits
  21. 01 Aug, 2019 1 commit