On 15 September 2016 at 20:12, Jon Turney <jon.tur...@dronecode.org.uk> wrote:
> On 15/09/2016 14:14, Emil Velikov wrote:
>> On 15 September 2016 at 13:06, Jon Turney wrote:
>>> Please consider pulling into master.
>>> The following changes since commit
>>> Hold input lock for deviceProc (2016-09-15 07:50:38 +1000)
>>> are available in the git repository at:
>>> for you to fetch changes up to 7280a41ef26647c27035e51e33c6f3ac5b12e931:
>>> Add Windows-DRI extension (2016-09-15 12:53:21 +0100)
>> Was meaning to mention this (mesa patches to be precise) but other
>> things keep on popping:
>> Where can one find the windowsdriproto package/repo that this depends on ?
> Like appledriproto, the headers and .pc currently live in mesa (under
> src/glx/windows) and are installed by that.
I'm pretty sure I mentioned/suggested the same thing for appledriproto
as well ;-)
> I did consider giving it an independent existence, but I'm not sure if
> that's wanted: there seemed to be a feeling that there are already too many
> proto repos, and it's not like these proto headers are likely to be used by
> anything else.
If people are afraid of "too many" proto repos, they always will be -
it makes no difference here. Yes, those are not be used by anything
else (atm) yet one shouldn't "clump" things based on that merit alone,
>> In there configure does not check for windowsdriproto, if the user
>> explicitly sets --enable-windowsdri, does it ?
>> Shouldn't one be using the windowsdriproto_CFLAGS to point to the headers
> Yes, my bad. I'll fix that.
Np. Glad I could help.
firstname.lastname@example.org: X.Org development