Package Details: mesa-git 24.3.0_devel.194818.d3429a7e00d.d41d8cd-1

Git Clone URL: https://aur.archlinux.org/mesa-git.git (read-only, click to copy)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL: https://www.mesa3d.org
Keywords: mesa wayland X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-clover-mesa, opencl-rusticl-mesa, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Provides: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-driver, opencl-rusticl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Submitter: Krejzi
Maintainer: rjahanbakhshi (Lone_Wolf)
Last Packager: Lone_Wolf
Votes: 182
Popularity: 0.39
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-09-15 20:40 (UTC)

Dependencies (53)

Required by (1302)

Sources (6)

Pinned Comments

Lone_Wolf commented on 2024-09-10 19:58 (UTC)

removed obsolete options, build now works again.

building opencl clover is disabled for now, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/11863

Those that need opencl should use rusticl instead. Note that rusticl at runtime is disabled by default, see https://docs.mesa3d.org/envvars.html#rusticl-environment-variables for info about enabling it.

Lone_Wolf commented on 2020-04-23 12:26 (UTC) (edited on 2023-03-30 07:04 (UTC) by Lone_Wolf)

Mesa and llvm are closely tied together. Everytime the llvm mesa is built against changes/updates , mesa needs to be rebuilt.

I expect anyone building mesa-git against one of the llvm trunk variants to be able to do that themselves, but atleast some of the people that built against repo llvm don't understand how to deal with such a rebuild.

The rest of this post is meant for those people.

  • Verify if latest PKGBUILD requirements match llvm repo versions.
  • If they don't , post to alert the maintainer of this.
  • DELAY the update of llvm/clang suite and their lib32- counterparts
  • Once the PKGBUILD does match, download it.

Option A - best one

  • run pacman -Syu to ensure your system is in sync with your mirrror server
  • build mesa-git in a clean chroot

see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot for the official way or https://aur.archlinux.org/packages/clean-chroot-manager for an alternative method.

  • install the newly built mesa-git
  • run pacman -Syu
  • ready

Option B - 2nd best

  • revert to repo mesa
  • pacman -Syu
  • build mesa-git
  • switch from mesa to mesa-git
  • ready

Lone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)

  • choosing which llvm variant to build against

WARNING : aur helpers don't support this method at all. They check .SRCINFO and that doesn't include this variable so it will use the default which is hardcoded to build against repo llvm.

Why would I want to use llvm development versions ?

For full functionality and latest features mesa trunk master needs to be build against llvm trunk master.
If you build against stable llvm things MAY work, but you're likely to lack some features and face stability issues.

Mesa-git uses a custom environment variable MESA_WHICH_LLVM for flexibility.
It has 4 values.
1 : aur llvm-minimal-git
2 : aur llvm-git
3: llvm-git from LordHeavy' unofficial repo
4: llvm from extra repo

I use value 1 95% of the time and set this in ~/.bash_rc .
If MESA_WHICH_LLVM is unset or empty, the default value of 4 (extra llvm) is used.

Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)

  • main difference with stable repo package
[extra]mesa is a split package, but aur mesa-git isn't.
Basically with aur mesa-git you get everything in one package, while [extra]/mesa allows you to leave out some parts if you don't want/need them.
Having a single package reduces maintenance and makes switching from stable to mesa-git rather easy, though reverting back to stable can be tricky.
  • meson settings
Those who compare PKGBUILDs will notice I don't use arch-meson, but meson setup.
I disagree with some of the settings made by arch-meson (especially the buildtype and enabling LTO by default) and feel using meson setup is cleaner.
  • how to update

run pacman Syu update non-repo packages for llvm if you use them

build mesa-git, log out , update mesa-git and restart X .

run glxinfo -B to verify basic OpenGL functionality

build lib32-mesa-git

run glxinfo32 -B to verify basic OpenGL functionality for multilib programs

Latest Comments

« First ‹ Previous 1 .. 80 81 82 83 84 85 86 87 88 89 90 .. 131 Next › Last »

Dr-Shadow commented on 2016-02-21 21:20 (UTC)

Hi, this package has a conflict with vulkan-intel (in extra) and should maybe be renamed into vulkan-intel-git. https://www.archlinux.org/packages/extra/x86_64/vulkan-intel/

haagch commented on 2016-02-19 13:53 (UTC)

Copy&paste error, one $pkgdir too much. Fixed now.

versusvoid commented on 2016-02-19 10:54 (UTC)

Building with yaourt results in broken symlink: > ll /etc/vulkan/icd.d/ total 4.0K lrwxrwxrwx 1 root root 100 Feb 19 13:11 intel_icd.json -> /tmp/yaourt-tmp-versus/aur-vulkan-i965-git/pkg/vulkan-i965-git/usr/share/vulkan/icd.d/intel_icd.json

1ace commented on 2016-02-19 09:17 (UTC)

Yes, I see that your using mesa's `make install `, but since most of those are already on mesa, your should `install` those three files instead.

haagch commented on 2016-02-19 00:09 (UTC)

I actually did this because I have not looked at the spec at all and someone on reddit told me that location. I just tried it in /usr/share/vulkan/icd.d/intel_icd.json and it doesn't seem to automatically be picked up. I'll leave a symlink in /etc/ until that works. It's just make install from mesa, maybe I can delete some of the files for the OpenGL libs... I changed to vulkan-icd-loader, so yea.

1ace commented on 2016-02-18 23:03 (UTC) (edited on 2016-02-18 23:31 (UTC) by 1ace)

Per spec [1], packages should install manifest files (*.json) in /usr/share/vulkan/icd.d /etc/vulkan/icd.d is for manually copied files [1] https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/blob/sdk-1.0.3/loader/LoaderAndLayerInterface.md#properly-installed-icds-1 Edit: now that I think about it, maybe you did this to leave the proper location open for when vulkan gets merged into mainline mesa? I guess you can just ignore me anyway, since this location works too :] Edit bis: I just finished compiling it, and I noticed you have way too many files in this package. The only 3 file that make sense are /etc/vulkan/icd.d/intel_icd.json, /opt/mesa-vulkan/lib/libvulkan_intel.so (which should go either in the same location as the .json, or in /usr/lib/) and /opt/mesa-vulkan/include/vulkan/vulkan_intel.h (which should go in /usr/include/vulkan/) Everything else is just redundant and will never be used in these location. You should also depend on `vulkan-icd-loader` (my package in the AUR (`vulkan-loader`) is not going to stay there once the couple bugs in the one in [extra] are fixed) and optdepend on `vulkan-headers` :)

haagch commented on 2016-02-18 22:44 (UTC)

Hm... Yea, I'll wait and see what "basename" to provide they decide on.

neuromancer85 commented on 2016-02-18 22:17 (UTC)

Could you change the dependency on vulkan-loader to vulkan-icd-loader from [extra]?

IncredibleLaser commented on 2016-02-18 18:36 (UTC) (edited on 2016-02-18 18:42 (UTC) by IncredibleLaser)

You're correct, python2-mako is a makedepends and so are python and git. Sounds silly since you need git anyways to use the AUR but if you build in a clean chroot it will throw you an error when trying to build.

Xabre commented on 2016-02-18 16:47 (UTC) (edited on 2016-02-18 16:50 (UTC) by Xabre)

checking if module mako in python is installed... No module named mako no configure: error: Python mako module v0.3.4 or higher not found Should depend on python-mako (probably just a makedep) Em, it's python2-mako, actually.