mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-04 13:30:11 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
fe2ec50844
This is done by introduce idep_vulkan_lite_runtime, and only venus depends on idep_vulkan_lite_runtime. Modify the meson and source files to allow building venus without the compiler. See details Venus build metrics at the MR description. gfxstream-vulkan forwards the shader to the host, and doesn't need to convert into NIR in the guest. This results in faster builds and less parts of Mesa to build. Also venus does the same thing too, that's what the build is keyed on right now as an in-tree user. v7: By Yonggang Luo <luoyonggang@gmail.com> Add idep_vulkan_common_entrypoints_h into vulkan_lite_runtime_deps because vk_instance.c depends on idep_vulkan_common_entrypoints_h but vk_common_entrypoints is not compiled in library `vulkan_lite_instance`. Rename idep_vulkan_runtime_headers to idep_vulkan_lite_runtime_headers because both lite/full runtime library depends on this, but lite should not depends on full vk_meta_private.h added into vulkan_runtime_files v6: By Yonggang Luo <luoyonggang@gmail.com> get vulkan_lite_runtime_files and vulkan_runtime_files sorted v5: By Yiwei Zhang <zzyiwei@chromium.org> both vk_sampler and vk_ycbcr_conversion can stay in the lite runtime v4: By Yonggang Luo <luoyonggang@gmail.com> only build vk_instance.(c|h) twice for reduce compiling time v3: By Yiwei Zhang <zzyiwei@chromium.org> less code changes by introduce libvulkan_lite_runtime v2: By Yonggang Luo <luoyonggang@gmail.com> allow building Vulkan without libcompiler without compiling flags, the venus is always built without libcompiler v1: By Gurchetan Singh <gurchetansingh@google.com> allow building Vulkan without libcompiler Signed-off-by: Gurchetan Singh <gurchetansingh@google.com> Signed-off-by: Yonggang Luo <luoyonggang@gmail.com> Signed-off-by: Yiwei Zhang <zzyiwei@chromium.org> Reviewed-by: Yiwei Zhang <zzyiwei@chromium.org> Reviewed-by: Yonggang Luo <luoyonggang@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26574> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| 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 | ||
| CODEOWNERS | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| 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://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja 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://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.