Skip to content

GitLab

Switch branch/tag
  1. 12 Nov, 2019 1 commit
  3. 11 Nov, 2019 2 commits
  5. 01 Nov, 2019 3 commits
  7. 03 Oct, 2019 1 commit
  9. 30 Sep, 2019 1 commit
  11. 26 Sep, 2019 2 commits
  13. 23 Sep, 2019 1 commit
  15. 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
  17. 16 Sep, 2019 1 commit
  19. 06 Sep, 2019 1 commit
  21. 26 Aug, 2019 1 commit
  23. 23 Aug, 2019 1 commit
  25. 22 Aug, 2019 1 commit
  27. 20 Aug, 2019 1 commit
  29. 19 Aug, 2019 2 commits
  31. 16 Aug, 2019 2 commits
  33. 15 Aug, 2019 2 commits
  35. 08 Aug, 2019 1 commit
  37. 07 Aug, 2019 15 commits