public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: build error on 1.16.2-1
Date: Fri, 05 Dec 2014 14:19:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 01/12/2014 23:37, J. Offerman wrote:
> This is an obvious source-header discrepancy. The source
> file(auto-generated anyway) doesn't seem to be changed recently, while
> the header file(glext.h) has a timestamp of Nov 16 now. So it looks
> like only the header file got advanced here. Looking at the
> announcements, it should be the Mesa update on Nov 17 that renewed it.
> Should I just add the extra arguments for those 3 funcs in the source
> file as defined in the new header file? That looks like working.

Thanks for drawing this to my attention.

Yes, it seems that the the glext.h header file (which comes from Khronos 
via the w32api-headers package) now has the fix (svn r27313) to add the 
extra argument to the prototype, but the XML used for the generated code 
(which comes from Khronos via the khronos-opengl-registry package) is 
only on svn r27116.

I'm afraid you'll have to fix this manually until I generate a new 
khronos-opengl-registry package

Since keeping these things in sync is kind of a pain, and limits it to 
handling GL functions which are known about at build time, I'd like to 
replace this compile-time thunk generation with something which does it 
dynamically at run-time, but I haven't found the time to do that...

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2014-12-05 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 19:09 J. Offerman
2014-12-01 23:37 ` J. Offerman
2014-12-05 14:19   ` Jon TURNEY [this message]
2015-01-31 14:22     ` Jon TURNEY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).