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

Dependencies (53)

Required by (1303)

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 .. 24 25 26 27 28 29 30 31 32 33 34 .. 131 Next › Last »

Lone_Wolf commented on 2022-07-11 22:12 (UTC)

d3d12 is in [extra]/mesa so could be considered for adding.

For the other 2 I completely agree with yuri : no wsl-exclusive stuff in aur .

yurikoles commented on 2022-07-11 21:13 (UTC)

@EndlessEden AUR has history to not welcome WSL-exclusive features.

EndlessEden commented on 2022-07-11 19:32 (UTC)

Please add: Gallium Driver d3d12 (Its used upstream as well) Vulkan Driver microsoft-experimental (DOZEN is a new API for using Vulkan on D3D12, necessary for WSL)

and Optional flag for microsoft-clc (useful for WSL)

Billli11 commented on 2022-07-02 21:03 (UTC) (edited on 2022-07-02 21:20 (UTC) by Billli11)

llvm and llvm-libs in official extra repo has been updated to 14.0.6-1

https://archlinux.org/packages/extra/x86_64/llvm/

Please update the PKGBUILD file.

Thanks

sir_randomuser commented on 2022-06-17 18:16 (UTC) (edited on 2022-06-17 19:41 (UTC) by sir_randomuser)

EDIT: this may only be relevant if you use LTO.

Hi everyone. Just wanted to give heads-up for folks with AMD GPU who build mesa-git together with the latest llvm-git - mesa would compile, but will not work and your DE would likely not start.

Related to this: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6615

The latest llvm-git I found working I built on May 28th. Just a heads up to use earlier llvm-git builds if you have them to compile mesa, or wait until mesa devs fix the issue.

Cheers

rjahanbakhshi commented on 2022-06-05 09:56 (UTC)

@miguel-rangel,

I don't see the issue in a clean build environment.

miguel-rangel commented on 2022-06-05 06:33 (UTC) (edited on 2022-06-05 06:42 (UTC) by miguel-rangel)

I was getting the following error:

Running custom install script '/bin/python '.../mesa-git/src/mesa/bin/install_megadrivers.py rm: cannot remove '../mesa-git/pkg/mesa-git/usr/bin/mesa-overlay-control.py': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... Its getting stuck because of this line in 163 of the PKGBUILD. This script is not in the directory. rm "${pkgdir}/usr/bin/mesa-overlay-control.py" when removed/commented out, the package should build

rjahanbakhshi commented on 2022-05-21 16:15 (UTC)

Hi @AkechiShiro,

Thanks for the report. Personally, I haven't seen this problem. But I removed lto flag for now until the bug is reported as fixed.