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

Dependencies (53)

Required by (1272)

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

1 2 3 4 5 6 .. 131 Next › Last »

00ein00 commented on 2024-09-21 12:40 (UTC)

Alright, it works now after adding options=(!lto) to directx-headers-git PKGBUILD.

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

I have found the issue that breaks build with directx-headers-git .

Please add options=(!lto) to the directx-headers-git PKGBUILD and rebuild it. (increasing pkgrel is probably also a good idea).

About removing the d3d12 optioin from mesa-git :

that decision should be made by @rjahanbakhshi aka Reza .

bluetail commented on 2024-09-21 01:37 (UTC) (edited on 2024-09-21 01:39 (UTC) by bluetail) 

Only builds when removing 'd3d12' from gallium-drivers=
Clean chroot did not help.

frogmech commented on 2024-09-19 19:19 (UTC)

@00ein00 It doesn't fail to build if you delete ",d3d12" from line 261 of the PKGBUILD

00ein00 commented on 2024-09-19 16:33 (UTC)

Think I'm having the same problem as ahrs https://0x0.st/X3wX.txt https://0x0.st/X3xz.txt

ahrs commented on 2024-09-19 06:11 (UTC)

This is currently failing to build for me due to a compilation error in the d3d12 support. I've disabled this locally in my builds for now but realistically is there any value in keeping this enabled by default? I assume this is here for WSL hosts on Windows but realistically how many people are running mesa-git there?

frogmech commented on 2024-09-16 11:33 (UTC)

Building in a clean chroot gives the same error, here's the full build log: https://0x0.st/X3KS.log

Lone_Wolf commented on 2024-09-16 09:42 (UTC) (edited on 2024-09-16 09:45 (UTC) by Lone_Wolf)

frogmech, 00ein00 : you both seem to have the same error .

Building in a clean chroot doesn't give this error, so it's unlikely to be a missing dep.

Please setup clean chroot building .

If that doesn't fail building you probably have installed something locally that screws up build (cmake comes to mind) or is to old.

Incase the clean chroot build fails also, post the mesa-git-*-build.log on a pastebin site like 0x0.st .

00ein00 commented on 2024-09-16 02:09 (UTC)

At first I was getting errors about needing directx-headers-git (I had the non-git version), after manually installing that, I'm still getting this error: https://0x0.st/X3HE.txt

Thoughts? is there a certain dependency to do with compiling that I'm missing? I'm totally lost here.

frogmech commented on 2024-09-15 23:42 (UTC)

I get this error while building: https://0x0.st/X3Hu.txt

Any ideas on how to fix it?

1 2 3 4 5 6 .. 131 Next › Last »