imho it would be a good feature if +opengl is set in the make.conf and the user tries to emerge qt - without running opengl-update first - to stop the qt-emerge. this can be done with "-e /usr/X11R6/include/GL/glext.h". the problem is that i did a "emerge kde" on a new system and it tried to build qt for serveral minutes before it told me that the qtext.h didn't exist. "wasting" this time could be prevented by such a check and the user knows that opengl-update is mandatory for emerging qt...
Can you attach a patch that provides this?
Created attachment 38016 [details, diff] warns about running opengl-update if USE="+opengl" and stops compiling tested it here and seams to work - but should be tested somewhere else also ;) and perhaps the "die" is not necessary.
just saw a typo in the patch ;) replace: "Qt meight will fail." with "Qt build meight fail." ...
What about this one? I tried to compile kdetv and did not remember to use opengl-update before (I changed for Xfree/ATI to Xorg). So QT was build whithout real opengl support and emerge kdetv failed. Whould be a nice feature. Best regards Jan
is this bug even valid anymore? opengl-update is run in postinst of opengl-update as well as in xorg-x11, ati-drivers, and nvidia-glx, so qt shouldn't expect it to be run, and virtual/opengl should satisfy anything it needs.
the xorg-x11 virtual/opengl is enough for qt to build but then it uses the xorg-opengl drivers for building instead of nvidia/ati drivers. so the bug is not valid any more in the way i reported it. atm the problem is that if you do a "emerge kde" on a clean system the nvidia/ati drivers won't be used. you have to do sth. like "emerge xorg-x11 nvidia kde" - or am i wrong? perhaps it would be good to have a +nvidia +ati switch for xorg-x11 that one of these driver gets installed after xorg-x11 and before other programs using opengl. like a post-depend (imho there is sth. like this in portage but don't know the name atm ;) on xorg-x11 ?
Re: >> but then it uses the xorg-opengl drivers for building instead of nvidia/ati drivers You don't USE drivers to compile. The ABI is the same for both, so compiling against one should have no difference from compiling against the other so long as the header files are compliant.
the header files looked very different - it seamed as there nvidida header supported more functions. i don't know, but isn't it possible to use the optional routines of nvidia/ati for compilation?
No, it doesn't work like that. The extensions are all in glext.h and glxext.h which are standardized. Both gl.h files should have the same effect, but they may be laid out differently because they're modified by different groups, BUT keep in mind the main thing is glext.h and glxext.h which is standardized.
