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 2 3 4 5 6 7 8 9 10 11 .. 131 Next › Last »

atticf commented on 2024-07-20 11:48 (UTC)

now requires python-yaml to build: (1 2)

Jelgnum commented on 2024-07-18 19:00 (UTC) (edited on 2024-07-18 19:15 (UTC) by Jelgnum)

The build flag swrast has been decomflated to llvmpipe,softpipe with this MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27607 and will be removed in mesa 25.0

Lone_Wolf commented on 2024-06-12 11:29 (UTC)

Coolian, please read the 'Pinned Comments' to find the answer.

Coolian commented on 2024-06-12 09:06 (UTC)

why is this in conflict with vulkan-radeon while the regular mesa package isnt?

Lone_Wolf commented on 2024-06-10 13:57 (UTC)

Beiruty commented on 2024-06-03 12:02 (UTC)

Is there an ETA for the fixed mesa-git PKG?

Lone_Wolf commented on 2024-05-17 22:36 (UTC)

Please have a bit of patience. Upstream is aware of the issue and working on a fix .

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

Billli11 commented on 2024-05-17 10:52 (UTC)

Find the cause of the problem.

rusticl now use output_inline_wrapper in meson for bindgen.

The include in created c file rusticl_mesa_bindings.c is a relative path,
and it's point to the source dir.
which cause incorrect path if the build dir is not inside the source dir.( which is the case in this AUR package ).

The current workaround is just build it inside mesa dir.

diff --git a/PKGBUILD b/PKGBUILD
index 68b0dac..701a628 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -216,10 +216,10 @@ pkgver() {
 }

 prepare() {
-    # although removing _build folder in build() function feels more natural,
+    # although removing mesa/_build folder in build() function feels more natural,
     # that interferes with the spirit of makepkg --noextract
-    if [  -d _build ]; then
-        rm -rf _build
+    if [  -d mesa/_build ]; then
+        rm -rf mesa/_build
     fi

     local _patchfile
@@ -278,13 +278,13 @@ build () {
     CFLAGS+=' -g1'
     CXXFLAGS+=' -g1'

-    meson setup mesa _build "${meson_options[@]}"
-    meson configure --no-pager _build
-    ninja $NINJAFLAGS -C _build
+    meson setup mesa mesa/_build "${meson_options[@]}"
+    meson configure --no-pager mesa/_build
+    ninja $NINJAFLAGS -C mesa/_build
 }

 package() {
-    DESTDIR="${pkgdir}" ninja $NINJAFLAGS -C _build install
+    DESTDIR="${pkgdir}" ninja $NINJAFLAGS -C mesa/_build install

     # remove script file from /usr/bin
     # https://gitlab.freedesktop.org/mesa/mesa/issues/2230

Coolian commented on 2024-05-17 08:55 (UTC)

Im having that same issue

DexterHaxxor commented on 2024-05-17 08:34 (UTC) (edited on 2024-05-17 08:34 (UTC) by DexterHaxxor)

Having the same issue, all Arch mesa packages seem to be broken ATM.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 131 Next › Last »