mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-24 17:08:20 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
1fe5838568
Fixes the following with meson2hermetic: src/freedreno/registers/adreno/a6xx_perfcntrs.py/genrule.sbox.textproto File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "gen_header.py", line 1220, in <module> File "gen_header.py", line 1216, in main File "gen_header.py", line 1177, in dump_py_defines File "gen_header.py", line 688, in parse File "gen_header.py", line 680, in do_parse File "external/python/cpython3/Modules/pyexpat.c", line 471, in StartElement File "gen_header.py", line 732, in start_element File "gen_header.py", line 673, in do_parse FileNotFoundError: [Errno 2] No such file or directory: './out/src/freedreno/registers/adreno/adreno_common.xml' Soong/Bazel `genrules` run in a separate sandbox, and require that all dependencies be explicitly declared. It is necessary for reproducible, hermetic and distributed builds. Meson prefers explicit dependency declaration too, but does not require it. For example, if `adreno_common.xml` is modified, and it is in `depend_files` for the `adreno_pm4.xml.h` custom_target, meson knows to re-gen `adreno_pm4.xml.h` during incremental builds. For freedreno, the custom targets in `src/freedreno/registers/*` don't declare all XML dependencies that are actually used. This patch fixes this. The other option is workaround this in meson2hermetic, but being more explicit conceptually more correct. Reviewed-by: Eric Engestrom <eric@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41518> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| src | ||
| subprojects | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-format-include | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| clippy.toml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| VERSION | ||
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.