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 .. 70 71 72 73 74 75 76 77 78 79 80 .. 131 Next › Last »

DiFuzZzoR commented on 2017-02-19 12:53 (UTC)

So, mesa-test* packages only for x86_64 arch? i686 abandoned to their fate? :(

cirk2 commented on 2017-02-18 21:51 (UTC)

yeah did the switchover from mesa-git and pulled in the staging mesa apparently.

Lone_Wolf commented on 2017-02-18 13:24 (UTC)

Cirk2, I guess you are referring to the libraries below that are included in mesa-17.0.0-2 package from [staging] repo ? My aur mesa trunk packages are intended to replace AL mesa packages in [extra] . dependencies are from core, community or AUR, never from testing or staging repos. Once the new method with GLVND enters official repos, these packages will change to it also. ----------------------------------- usr/lib/libEGL_mesa.so usr/lib/libEGL_mesa.so.0 usr/lib/libEGL_mesa.so.0.0.0 usr/lib/libGLX_mesa.so usr/lib/libGLX_mesa.so.0 usr/lib/libGLX_mesa.so.0.0.0 usr/lib/libOSMesa.so usr/lib/libOSMesa.so.8 usr/lib/libOSMesa.so.8.0.0

cirk2 commented on 2017-02-18 13:00 (UTC) (edited on 2017-02-18 13:23 (UTC) by cirk2)

The package seems not to compile/install libGLX_mesa.so is there a deeper reason for this? edit: never mind the old mesa install killed it when replacing it, reinstall of xorg-server fixed it.

Lone_Wolf commented on 2017-02-13 15:32 (UTC)

Sorry for not being clearer. Kerberizer is correct, the current PKGBUILD is deprecated. mesa-test-git is fully uptodate and has been used on my personal systems for 2+ months without any problems. Once AL has switched to GLVND, we might even be able to get rid of the *-libgl-git stuff and have mesa-git become a simple not-splitted package. @linkmauve : thanks for the link, i was not aware that list existed. subscribed.

kerberizer commented on 2017-02-13 14:21 (UTC)

@linkmauve, I believe this package is now considered deprecated. As mentioned by @Lone_Wolf, users should switch to mesa-test-git (or just wait for it to be merged here in two weeks). I've been using the mesa-test-git and lib32-mesa-test-git packages from the very beginning and can attest that they are trouble-free (at least for my setup, of course).

linkmauve commented on 2017-02-13 14:09 (UTC)

Also please subscribe to mesa-maintainers@lists.freedesktop.org to get notifications whenever the build options change, so users won’t get a broken package at any time.

linkmauve commented on 2017-02-13 14:08 (UTC)

Hi, the --with-sha1 option has been removed, as well as its previous value of nettle: a sha1 implementation is now built in-tree. Here is the warning if you pass this option: configure: WARNING: unrecognized options: --with-sha1

Lone_Wolf commented on 2017-02-13 12:00 (UTC)

Package fails to build atm due to the removal of ilo driver code. I have been working on a new improved git package for mesa, please switch to mesa-test-git / lib32-mesa-test-git. In approx 2 weeks (28 february) i will request mesa-test-git to be merged into this package.

Lone_Wolf commented on 2017-02-05 16:59 (UTC)

@Hi-Angel : the source url used in mesa-git was not in line with vcs pacakge guidelines, when i started this package i changed both mesa-git & mesa-test-git . gallium and dri drivers : all modern amd cards use gallium drivers, but drivers for older cards were not ported to gallium. Although the last r200 card was manufactured in 2004, it still gets commits and continues to be supported (stock arch mesa also supports it).