Those of us trying to get digikam plugins to work ran into problems with Qt, which were resolved when removing the "-dlopen-opengl" flag from the Gentoo ebuild. From the configure, it looks like this is the default setting: * -no-dlopen-opengl .. Qt links against OpenGL libraries directly. -dlopen-opengl ..... Qt uses dlopen(3) to resolve OpenGL functions (instead of linking with OpenGL libraries directly). I'm no OpenGL expert, but why not link against OpenGL directly?
The reason it's done this way is because a lot of people use the nvidia drivers, which comes with its own version of GL, which isn't binary compatible. So they build their system, then install the nvidia drivers, then use a qt program, and complain about it crashing. This fixed that. I suppose we need to look into offering it via a configuration option.
True. For some reason I thought there was an 'nvidia' USE flag that would be usable but now that I check I guess it was all in my head. I wonder if those digikam plugins build on an nvidia system with the current Qt setup.
Also with this option it is possible to prelink qt even if you use the (not prelinkable) nvidia drivers.
Is that digikam plugin the only program that needs the direct link to the OpenGl-libs? There are other Qt-based progs which use OpenGL and work pretty fine with -dlopen-opengl. How do they resolve this? The digikamplugin problem is resolved now by using -lGL directly
I believe that the digikam situation is resolved and this may be closable? I don't use digikam anymore so I can't say.
sounds safe to close to me.
