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.40
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-09-15 20:40 (UTC)

Dependencies (53)

Required by (1306)

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 .. 10 11 12 13 14 15 16 17 18 19 20 .. 131 Next › Last »

therealmate commented on 2024-01-29 17:25 (UTC)

Any reason why lto is still disabled? repo mesa has it on by default for a while now:https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/b76de265631c7b21296c26628a47e2cf3aa01b60

Lone_Wolf commented on 2023-12-20 19:25 (UTC)

Mesa opencl methods clover & rusticl depend on them, but other then that there's very little that needs spirv-llvm-translator and liblcl .

Opencl is not used in games as far as I know, so spirv-llvm-translator & libclc are not needed for gaming (native/steam/proton etc ).

d3vilguard commented on 2023-12-20 04:42 (UTC)

Should one bother compiling spirv-llvm-translator and libclc if only usage is Proton gaming? Sorry for the newbie question.

Lone_Wolf commented on 2023-12-18 20:41 (UTC) (edited on 2023-12-18 20:42 (UTC) by Lone_Wolf) 

$ pacman -Si directx-headers | grep Version
Version         : 1.611.0-1
$

archlinux repos do have 1.611.0 , so those other distros are lagging behind.

As for directx-headers-git : as normal for -git packages it builds the very latest commit.

Currently that is https://github.com/microsoft/DirectX-Headers/commit/48f23952bc08a6dce0727339c07cedbc4797356c which provides 1.611.1 .

deemon commented on 2023-12-18 16:35 (UTC) (edited on 2023-12-18 16:36 (UTC) by deemon)

This one requires directx-headers 1.611+ but the most common one is 1.610 (in manjaro extra, and AUR -cmake and mingw versions). And some weird AUR -git version 181 (no, not 1.810 but 181?), whatever that provies. Does it work/build with the AUR directx-headers-git?

edtoml commented on 2023-11-30 13:52 (UTC) (edited on 2023-12-04 00:37 (UTC) by edtoml)

If you want to build this for 23.3 you will need to change two things:

(1)change main to 23.3 or staging/23.3

source=('mesa::git+https://gitlab.freedesktop.org/mesa/mesa.git#branch=23.3'

(2)remove av1dec,av1enc,vp9dec

-D video-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc \

lib32-mesa-git just needs 1.

rjahanbakhshi commented on 2023-11-29 09:13 (UTC)

@Billli11,

Thanks, those codecs are now explicitly enabled in the PKGBUILD.

Billli11 commented on 2023-11-21 04:30 (UTC)

With Merged MR 26223

The following value is added to video-codecs 'av1dec', 'av1enc', 'vp9dec'

Av1 and vp9 hardware acceleration is no longer enable by default.

--- a/src/gallium/auxiliary/vl/vl_codec.c
+++ b/src/gallium/auxiliary/vl/vl_codec.c
@@ -32,6 +32,20 @@ bool vl_codec_supported(struct pipe_screen *screen,
                         enum pipe_video_profile profile,
                         bool encode)
 {
+   static_assert(PIPE_VIDEO_PROFILE_MAX == 26, "Update table below when adding new video profiles");
+   if (profile == PIPE_VIDEO_PROFILE_AV1_MAIN) {
+      if (encode) {
+         if (!VIDEO_CODEC_AV1ENC)
+            return false;
+      } else if (!VIDEO_CODEC_AV1DEC) {
+         return false;
+      }
+   }
+   if (profile == PIPE_VIDEO_PROFILE_VP9_PROFILE0 ||
+       profile == PIPE_VIDEO_PROFILE_VP9_PROFILE2) {
+      if (!VIDEO_CODEC_VP9DEC)
+         return false;
+   }
    if (profile == PIPE_VIDEO_PROFILE_VC1_SIMPLE ||
        profile == PIPE_VIDEO_PROFILE_VC1_MAIN ||
        profile == PIPE_VIDEO_PROFILE_VC1_ADVANCED) {

Abiding0550 commented on 2023-11-08 15:04 (UTC)

@Lone_Wolf thanks! Now it works! :)

Lone_Wolf commented on 2023-11-08 11:19 (UTC)

@maintuner : Comments tend to fall down fast, maybe email the proposal ?

@Abiding0550

from https://wiki.archlinux.org/title/Arch_User_Repository#Prerequisites

Note: Packages in the AUR assume that base-devel is installed in the build environment.

install base-devel then try again.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 131 Next › Last »