Home/ Questions/Q 3392036
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T03:52:23+00:00

Most applications (and libraries) using OpenGL on Linux load libGL.so at runtime using dlopen

  • 0

Most applications (and libraries) using OpenGL on Linux load libGL.so at runtime using dlopen API, instead of dynamically linking against it.

Why do they do this?

The only reason I can imagine is that it’s because any graphic driver vendor provides a different libGL, and two different libGL could be ABI incompatible. (Well, hum, why should they be ABI incompatible? And even if they are, why loading them via dlopen would fix this issue?)

Anyway, supposing there’s a good reason for doing that, I’d like to do that as well. Does anybody have a link to an opensource C/C++ code that loads all the OpenGL functions via dlopen, which I can include to my project without needing too many tweaks?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are two main reasons people do this:

    1. You can give a sensible error for systems that don’t have OpenGL
    2. Vendors offer many different extensions and the only sane way to support multiple sets of extensions without different binaries per vendor is to use dlsym to check for them. GLEW offers a nice way of doing this for you though.
    • 0