Khronos public bugtracker – Bug 753
FRAMEBUFFER_ATTACHMENT_TEXTURE_LAYER should not be in VERSION_3_2
Last modified: 2013-06-13 03:46:30 PDT
The enumext.spec file shows FRAMEBUFFER_ATTACHMENT_TEXTURE_LAYER in both VERSION_3_0 and VERSION_3_2. It should just be in 3_0. No other enumerators are listed under multiple versions.
This was probably incorporated due to their presence in ARB_geometry_shader4 when GS's were brought into core. However, these extensions were incorporated from ARB_framebuffer_object in core 3.0, so there's no reason to specify them twice in versions.
This error makes it difficult to determine what the actual version number for the extension was, for making automated tools for generating accurate headers with specific versioning info.
Note that MAX_VARYING_COMPONENTS has the same problem.
This should be fixed in the new XML API Registry and in the
headers generated from that; see
We don't plan to maintain the old .spec files going forward and it
will not be fixed there; we'd like people to migrate to using the
XML registry for whatever external purposes they might be using
.spec for today, because .spec files are just too painful for us
to keep maintaining.