Build & install
---------------
-You can find more information in our documentation (`docs/install.html
+You can find more information in our documentation (`docs/install.rst
<https://mesa3d.org/install.html>`_), but the recommended way is to use
-Meson (`docs/meson.html <https://mesa3d.org/meson.html>`_):
+Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_):
.. code-block:: sh
-----------
If you think something isn't working properly, please file a bug report
-(`docs/bugs.html <https://mesa3d.org/bugs.html>`_).
+(`docs/bugs.rst <https://mesa3d.org/bugs.html>`_).
Contributing
------------
Contributions are welcome, and step-by-step instructions can be found in our
-documentation (`docs/submittingpatches.html
+documentation (`docs/submittingpatches.rst
<https://mesa3d.org/submittingpatches.html>`_).
Note that Mesa uses gitlab for patches submission, review and discussions.
`mesa-dev <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`__
mailing list.
#. Start contributing to the project by `submitting
- patches <submittingpatches.html>`__. Specifically,
+ patches <submittingpatches.rst>`__. Specifically,
- Use `gitlab <https://gitlab.freedesktop.org/>`__ to create your
merge requests.
- Patches should not mix code changes with code formatting changes
(except, perhaps, in very trivial cases.)
- Code patches should follow Mesa `coding
- conventions <codingstyle.html>`__.
+ conventions <codingstyle.rst>`__.
- Whenever possible, patches should only affect individual Mesa/Gallium
components.
- Patches should never introduce build breaks and should be bisectable
nomination request.
The current patch status can be observed in the `staging
-branch <releasing.html#stagingbranch>`__.
+branch <releasing.rst#stagingbranch>`__.
The stable tag
~~~~~~~~~~~~~~
numbers to represent your measurements.
If the patch complies with the rules it will be
-`cherry-picked <releasing.html#pickntest>`__. Alternatively the release
+`cherry-picked <releasing.rst#pickntest>`__. Alternatively the release
manager will reply to the patch in question stating why the patch has
been rejected or would request a backport. The stable-release manager
may at times need to force-push changes to the stable branches, for
Software drivers include:
-- `llvmpipe <llvmpipe.html>`__ - uses LLVM for x86 JIT code generation
+- `llvmpipe <llvmpipe.rst>`__ - uses LLVM for x86 JIT code generation
and is multi-threaded
- softpipe - a reference Gallium driver
-- `svga <vmware-guest.html>`__ - driver for vmware virtual gpu
+- `svga <vmware-guest.rst>`__ - driver for vmware virtual gpu
- `swr <https://www.openswr.org/>`__ - x86-optimized software renderer
for visualization workloads
- `virgl <https://virgil3d.github.io/>`__ - research project for
- `DRI hardware drivers <https://dri.freedesktop.org/>`__ for the X
Window System
-- `Xlib / swrast driver <xlibdriver.html>`__ for the X Window System
+- `Xlib / swrast driver <xlibdriver.rst>`__ for the X Window System
and Unix-like operating systems
- `Microsoft Windows <README.WIN32>`__
.. note::
Changes for Mesa 6.4 and later are documented in the corresponding
- `release notes <relnotes.html>`__ file.
+ `release notes <relnotes.rst>`__ file.
1.0 beta February 1995
----------------------
.. note::
Changes for Mesa 6.4 and later are documented in the corresponding
- `release notes <relnotes.html>`__ file.
+ `release notes <relnotes.rst>`__ file.