Package Details: mesa-git 25.2.0_devel.204321.de6efc01c12.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: rjahanbakhshi
Votes: 188
Popularity: 2.00
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-04-16 20:46 (UTC)

Dependencies (52)

Required by (1331)

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 .. 42 43 44 45 46 47 48 49 50 51 52 .. 134 Next › Last »

fisch02 commented on 2020-06-02 13:28 (UTC) (edited on 2020-06-02 13:38 (UTC) by fisch02)

Since https://gitlab.freedesktop.org/mesa/mesa/-/commit/138c003d22739b0d1e6860ed398dd511a44cde04, "true" and "false" were deprecated in favor of "enabled" and "disable" for some options. This throws a warning of the form "WARNING: (Optionname) option "true" deprecated, please use "enabled" instead." during build. The build() function of the PKGBUILDs for mesa-git and lib32-mesa-git should therefore be edited correspondingly. EDIT: Btw. with issue #2977 being closed, lto could now be enabled again

ph34rb0t commented on 2020-05-18 18:48 (UTC)

Yes, that bug report set me onto the right track regarding lto.

Thanks for the PKGBUILD fix!

Lone_Wolf commented on 2020-05-17 22:48 (UTC) (edited on 2020-05-17 22:49 (UTC) by Lone_Wolf)

Yep, mesa , lto and gcc 10.1 don't seem to work together.

see https://bugs.archlinux.org/task/66666 and https://gitlab.freedesktop.org/mesa/mesa/-/issues/2977

Disabled lto in this package, will do lib32-mesa-git soon.

ph34rb0t commented on 2020-05-16 15:59 (UTC) (edited on 2020-05-16 16:38 (UTC) by ph34rb0t)

I had to set "-D b_lto=true" to "false" in the PKGBUILD to prevent Plasmashell and any OpenGL app (e.g. glxinfo, glxgears) from crashing. (Built against the standard llvm and llvm-libs packages.)

(Edited original post with solution and made it more concise.)

gort818 commented on 2020-05-15 14:29 (UTC)

Yes it is.

Lone_Wolf commented on 2020-05-15 10:07 (UTC)

Is https://gitlab.freedesktop.org/mesa/mesa/-/issues/2958 the bugreport you filed ?

gort818 commented on 2020-05-14 22:47 (UTC)

@Lone_Wolf I have already filed a bug report.

My system only has one vulkan capable card.

I tired MESA_VK_DEVICE_SELECT=0 for good measure and no luck.

Lone_Wolf commented on 2020-05-14 09:59 (UTC)

@gort818 Mesa 20.1 (currently in rc phase) will support that option, could you file bugreports ?

Does your system have one or more vulkan capable cards ?

If more then one, try MESA_VK_DEVICE_SELECT=list vulkaninfo to find out which ids the cards have.

You should then be able to assign a specific one to the game which may solve the issue.

gort818 commented on 2020-05-14 03:07 (UTC)

vulkan-device-select-layer=true has caused issues launching some of my games, after I set it to false no problems.

Lone_Wolf commented on 2020-05-08 20:43 (UTC) (edited on 2020-05-08 22:27 (UTC) by Lone_Wolf)

Mesa-git is currently broken on some types of cards (including all polaris10 /RX580 ).

https://gitlab.freedesktop.org/mesa/mesa/-/issues/2920

Solved with https://gitlab.freedesktop.org/mesa/mesa/-/commit/1a59590e5d686a11687151d57f2fd43d366d6720

« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 134 Next › Last »