Lines Matching defs:code
19 \def\code#1{{\tt #1}}
59 often used for additional purposes such as library code generators or
69 \code{make} and generate C/C++ header files for all the following
73 \item \code{GL/glext.h} - OpenGL 1.2 (and later) compatibility profile
75 \item \code{GL/glcorearb.h} - OpenGL core profile API + extensions
76 \item \code{GLES/gl.h} - OpenGL compatibility profile API
77 \item \code{GLES/glext.h} - OpenGL ES 1.x extensions
78 \item \code{GLES2/gl2.h} - OpenGL ES 2.x API
79 \item \code{GLES2/gl2ext.h} - OpenGL ES 2.x extensions
80 \item \code{GLES3/gl3.h} - OpenGL ES 3.x API
81 \item \code{GL/glx.h} - GLX API
82 \item \code{GL/glxext.h} - GLX 1.3 (and later) API + extensions
83 \item \code{GL/wgl.h} - WGL API
84 \item \code{GL/wglext.h} - WGL extensions
85 \item \code{EGL/egl.h} - EGL (still being worked on)
88 Starting with the Makefile rules and inspecting the files \code{gl.xml},
89 \code{genheaders.py}, and \code{reg.py} will be necessary if you want to
100 \subsection{Header Generation Script - \code{genheaders.py}}
102 When generating header files using the \code{genheaders.py} script, an
107 \code{genheaders.py} contains predefined generator options for OpenGL compatibility
115 \subsection{Registry Processing Script - \code{reg.py}}
117 Actual XML registry processing is done in \code{reg.py}, which contains
132 schema file, \code{registry.rnc}, against which the XML registry files
138 \item OpenGL and OpenGL ES - \code{gl.xml}
139 \item GLX - \code{glx.xml}
140 \item WGL - \code{wgl.xml}
141 \item EGL - \code{egl.xml} (still in development)
159 name. As used in \code{genheaders.py} and \code{gl.xml}, the API names
160 are \code{gl}, \code{gles1}, and \code{gles2}, corresponding to OpenGL,
210 Each \tag{type} tag contains legal C code, with attributes or embedded
227 \tag{type} contains text which is legal C code for a type declaration.
383 together, currently unused but typically something like \code{GL}
388 present in the is \code{bitmask}.
445 specific type. Currently only \code{u} and \code{ull} are used,
446 for \code{unsigned} 32- and 64-bit integer values, respectively.
507 \code{GL}.
548 names which resolve to the {\bf same} client library code, so (for
554 \code{glVertex3f} is \code{glVertex3fv}.
580 legal C code describing the return type and name of a command. In addition
623 legal C code describing the type and name of a function parameter. In
670 section~\ref{schema:apiname}), such as \code{gl} or \code{gles2}.
673 inclusion. Example: \code{GL\_VERSION\_4\_2}.
680 interpreted as $majorNumber.minorNumber$. Example: \code{4.2}.
706 When processed into a C header for the \code{compatibility} profile of
723 If processed into a header for the \code{core} profile, the definition of
724 \code{GL\_INDEX} would not appear.
750 specification, such as \code{ARB\_multitexture}. \tag{extension} is
760 \code{\^{}} and \code{\$} bracketing it, which should match the
793 either the GL compatibility (\code{gl}) or GL core (\code{glcore}) API
795 \code{core} profile of OpenGL, this results in (assuming the usual
886 \code{gl.xml} will evolve in response to schema changes, to new
891 to the \code{.xml} files will be described in Github revision history.
911 \subsection{Type Annotations and Relationship to \code{.spec} Files}
915 and array length information from the old \code{.spec} files, which
934 The \tag{group}s added to \code{gl.xml} are the enumerant groups defined
935 in \code{enum.spec}, and \code{enumext.spec}. Many additional group
936 names were used in the annotations in \code{gl.spec}, and they
943 entirely out of \code{gl.xml}, since they offer no useful additional
946 For example, a parameter described as \code{UInt32} in \code{gl.spec} is
947 not annotated with \code{group="UInt32"} in \code{gl.xml}, because this
949 declaration as \code{<ptype>GLuint</ptype>}.
951 A few examples of such groups are \code{cl\_context},
952 \code{handleARB}, \code{Int32}, and \code{sync}.
962 This is not a regression relative to the \code{.spec} files, which also
965 A few examples of such groups are \code{CheckedFloat32},
966 \code{ClampedFixed}, and \code{CoordD}.
972 \code{glGen*} command, such as a display list name, are retained in in
977 This is not a regression relative to the \code{.spec} files, which also
980 A few examples of such groups are \code{List} and \code{Path}.
986 \code{enum.spec} and \code{enumext.spec} are retained in \tag{proto} and
988 groups usually are a result of vendors contributing \code{gl.spec}
990 \code{enum.spec} entries.
992 This is not a regression relative to the \code{.spec} files, which also
995 A few examples of such groups are \code{ArrayObjectPNameATI},
996 \code{BinormalPointerTypeEXT}, and \code{SpriteParameterNameSGIX}.
1001 There are probably a few groups which are present in \code{gl.xml} but
1007 The \code{genheaders.py} script has been enhanced to allow validating
1009 \code{-validate} option, for example via:
1011 \code{\$ genheaders.py -validate -registry gl.xml}