<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 11/24/2015 02:49 PM, Emil Velikov wrote: <blockquote cite="mid:CACvgo53RmwRFSec1-Rwa8tw1TcTvNUCvMFoBLoXp5hS=tBZCVA@mail.gmail.com" type="cite"> <pre wrap="">On 24 November 2015 at 20:22, Kyle Brenneman <a class="moz-txt-link-rfc2396E" href="mailto:kbrenneman@nvidia.com"><kbrenneman@nvidia.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">On 11/13/2015 12:50 PM, Kyle Brenneman wrote: </pre> </blockquote> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">I agree that a separate directory from the other GL headers would be best. I'm leaning toward putting the libglvnd headers into a sibling directory to the GL headers, probably /usr/include/GLVND. Putting them in a subdirectory under GL (/usr/include/GL/GLVND) would also be an option. But eventually, libglvnd will have an EGL header there as well, and putting that under /usr/include/GL seems less appropriate. Does that sound like a good place for them? Does anyone have any thoughts or opinions on this? </pre> </blockquote> <pre wrap="">Sorry about the delay. I've missed your previous email. Keeping GLVND and GL, EGL, etc. separate sounds like the better option. I kind of hinted about that earlier :-P But seriously, I'm not sure about the exact state glvnd itself although I will be taking a closer look one the mesa side. I'm afraid that I have a few other items on my todo list before that. Thanks Emil P.S. Hmmm Gmail seems unhappy with flowed format emails :-( </pre> </blockquote> Okay, I'll use a sibling directory for now, then. It'll be easy enough to change later if need be, and a pkgconfig file should make it easy for other builds to deal with any changes. I also still need to update the example libglvnd-based Mesa to match the changes to libglvnd itself. I'll try to get that done by today or tomorrow, though. -Kyle </body> </html>