<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - protocol: GLES library are wayland protocol dependent" href="https://bugs.freedesktop.org/show_bug.cgi?id=97624#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - protocol: GLES library are wayland protocol dependent" href="https://bugs.freedesktop.org/show_bug.cgi?id=97624">bug 97624</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>Hi, I don't think downgrading a library is generally supported on any software across minor version number changes. Just to get this straight: you built your library against 1.11.0 and attempted to run it against 1.9.0, yes? If you build against a new library version which has bumped the minor version number, you cannot usually assume that you can still run it against a library version with a smaller minor number. The other direction we do try hard to keep things working: build against older library and run against a newer library. Only major version bumps can break that, and we do not intend to bump major on any libwayland. We also try to ensure that having a library built against one libwayland version and another library or the executable itself built against a different libwayland version also work when loaded into the same process, but we do not have the facilities to actually test that. So, yes, if you build your software against a libwayland version, then it will generally require at least that libwayland version. It is also assumed that you use wayland-scanner of the same version as you will build your software with. If you are checking in files generated with wayland-scanner into your VCS, please stop doing that and instead run wayland-scanner as part of the build. That way it is much easier to keep your software both up-to-date and compatible with several libwayland versions. The scanner can and will use new features added in the release it was part of, so simply re-running the scanner can bump your dependency to libwayland. If you cannot bump your library dependencies, you have to continue building against libwayland 1.9.0.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>