Hello, Sorry for the delay.
On 2024/02/04 00:39:10 -0400, Jose Maldonado <josemal...@gmail.com> wrote: > El Sat, 03 Feb 2024 12:25:31 +0100 > Omar Polo <o...@omarpolo.com> escribió: > > On 2024/01/24 11:07:12 +0100, Omar Polo <o...@omarpolo.com> wrote: > > > the changelog is available here: > > > > > > https://github.com/yshui/picom/releases/tag/v11-rc1 > > > > > > picom now tries to set itself as real-time. I've commented out that > > > part since it uses a function we don't seem to provide > > > (sched_setscheduler), but it's not a big deal. > > > > > > However, I had again issues with the visibility of OpenGL symbols. > > > This time the 'usual' workaround didn't work. See the two diffs > > > below. It's ugly, but at least I can confirm that the glx backend > > > works for me (amdgpu if it matters.) Any help understanding this > > > is welcome :) > > > > diff updated for 11.1, still no idea regarding the > > glGetQueryObjectui64v symbol issue. > > > > Update, I have successfully managed to compile and run picom-v11.1 with > the following changes. Take a look and feedback is welcome! I haven't tested the diff (yet), but thanks for working on it! I find it curious that glGetQueryObjectuiv is exported and glGetQueryObjectui64v is not. However if upstream is expecting an uint64, I'm not sure that silently changing it to a int is a sensible thing to do, especially since it seems to be a timestamp. It would probably be safer to ask upstream about this and see if they have a clue. Let me know if you prefer to do it, otherwise I can ask them. Thanks, Omar Polo
