vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
38 lines
1.4 KiB
ReStructuredText
38 lines
1.4 KiB
ReStructuredText
Development Notes
|
|
=================
|
|
|
|
Adding Extensions
|
|
-----------------
|
|
|
|
To add a new GL extension to Mesa you have to do at least the following.
|
|
|
|
- If ``glext.h`` doesn't define the extension, edit ``include/GL/gl.h``
|
|
and add code like this:
|
|
|
|
.. code-block:: c
|
|
|
|
#ifndef GL_EXT_the_extension_name
|
|
#define GL_EXT_the_extension_name 1
|
|
/* declare the new enum tokens */
|
|
/* prototype the new functions */
|
|
/* TYPEDEFS for the new functions */
|
|
#endif
|
|
|
|
|
|
- In the ``src/mesa/glapi/glapi/gen/`` directory, add the new extension
|
|
functions and enums to the ``gl_API.xml`` file. Then, a bunch of
|
|
source files must be regenerated by executing the corresponding
|
|
Python scripts.
|
|
- Add a new entry to the ``gl_extensions`` struct in ``consts_exts.h`` if
|
|
the extension requires driver capabilities not already exposed by
|
|
another extension.
|
|
- Add a new entry to the ``src/mesa/main/extensions_table.h`` file.
|
|
- From this point, the best way to proceed is to find another
|
|
extension, similar to the new one, that's already implemented in Mesa
|
|
and use it as an example.
|
|
- If the new extension adds new GL state, the functions in ``get.c``,
|
|
``enable.c`` and ``attrib.c`` will most likely require new code.
|
|
- To determine if the new extension is active in the current context,
|
|
use the auto-generated ``_mesa_has_##name_str()`` function defined in
|
|
``src/mesa/main/extensions.h``.
|