On Fri, 2018-06-15 at 11:23 -0600, Kyle Brenneman wrote: > The Khronos repository basically is a package for the headers. The > challenge is that the pkg-config file has to specify an include path and > a library path. The include path depends on where you put the header > files (which are in the Khronos repository), but library path depends on > how you configure libglvnd. > > The libglvnd tree probably does make the most sense: That's where the > libraries are from, and so it should be the only thing you need to build > and link an OpenGL application. It also has a copy of the GL header > files that it uses to build. It could install those copies, but the > challenge then is keeping libglvnd's copy of the header files up to date.
To be honest, that's something that needs better automation anyway. Epoxy and Mesa want to track the xml updates closely too. I've set up cron jobs in travis to check daily whether the xml has been changed, so I'll at least get notifications: https://travis-ci.org/nwnk/OpenGL-Registry https://travis-ci.org/nwnk/EGL-Registry It would be good to close the loop there and automate the process of importing the XML, rebuilding, checking for ABI breaks... - ajax _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
