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

schlunze commented on 2022-10-01 14:29 (UTC) (edited on 2022-10-01 14:35 (UTC) by schlunze)

i got trouble to compile this package in a clean chroot

mesa/meson.build:21:0: ERROR: Unknown options: "gallium-xvmc"

A full log can be found at /build/mesa-git/src/_build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...

EDIT --> Thank you Cloudperry remove the line worked - comment out does not work :) greetings

Cloudperry commented on 2022-10-01 13:07 (UTC)

It seems that this package needs to be updated after latest Mesa changes to make it build again. This is the reason for the build failure. The build errors like this:

==> Starting build()...
The Meson build system
Version: 0.63.2
Source dir: /home/roni/.cache/paru/clone/lib32-mesa-git/src/mesa
Build dir: /home/roni/.cache/paru/clone/lib32-mesa-git/src/_build
Build type: native build
Program python3 found: YES (/usr/sbin/python3)

mesa/meson.build:21:0: ERROR: Unknown options: "gallium-xvmc"

A full log can be found at /home/roni/.cache/paru/clone/lib32-mesa-git/src/_build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'lib32-mesa-git-22.3.0_devel.160382.e24a8168189.d41d8cd98f00b204e9800998ecf8427e-1':
error: packages failed to build: mesa-git-22.3.0_devel.160382.e24a8168189.d41d8cd98f00b204e9800998ecf8427e-1  lib32-mesa-git-22.3.0_devel.160382.e24a8168189.d41d8cd98f00b204e9800998ecf8427e-1

The PKGBUILD can be fixed by removing this line inside the build function:

       -D gallium-xvmc=disabled \

The same change should be applied to lib32-mesa-git.

rjahanbakhshi commented on 2022-09-24 11:02 (UTC)

@AtticFinder65536,

Sorry for the late response. I added intel_hasvk Vulkan driver to the PKGBUILD as you suggested.

atticf commented on 2022-09-13 09:30 (UTC)

I suggest adding the intel_hasvk Vulkan driver since it was split from intel two weeks ago in main. It is needed for hardware Vulkan support on Intel Haswell graphics.

rjahanbakhshi commented on 2022-08-11 15:11 (UTC)

Gallium Driver d3d12 added as upstream DirectX headers for using D3D12 problem is fixed in 1.606.3

rjahanbakhshi commented on 2022-08-11 08:53 (UTC)

Your package mesa-git [1] has been flagged out-of-date by bittin [2]:

22.2.0-rc2 released

@bittin,

Why do you keep flagging this package as out-of-date? This is a git package so it directly compiles the latest code from the mesa's main branch tip. It doesn't have anything to do with the releases you mention in your message. Just build and install it and it should work. If not, then let me know.

rjahanbakhshi commented on 2022-07-21 19:04 (UTC) (edited on 2022-07-21 19:05 (UTC) by rjahanbakhshi)

@HazardousBit,

I don't know what you mean by "this patch", but if you want to add a patch, just put the patch file in the same directory as the PKGBUILD and add the patch file name to the source array. The patch file extension should be '.patch' otherwise prepare function won't pick it up. After that, simply run 

updpkgsums
makepkg --printsrcinfo > .SRCINFO
makepkg -sri

If that doesn't work, share your patch and PKGBUILD here so I can take look.

HazardousBit commented on 2022-07-21 18:43 (UTC)

I'm trying to apply this patch but makepkg is not detecting the file and skipping the patch. Pardon my ignorance, but is there anything else I need to do to apply a patch?

EndlessEden commented on 2022-07-13 23:02 (UTC)

@yurikoles - Ouch, unaware of that; thanks for the info. Unfortunately i have to use WSL at work, so Ill maintain a separate fork locally for those features.

@rjahanbakhshi - Thanks; still helpful for the timebeing and i was unaware of issue 6733.

rjahanbakhshi commented on 2022-07-12 09:01 (UTC)

I agree with adding d3d12 and no wsl-exclusive stuff in aur.
d3d12 build is broken at the moment. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/6733

I'll add it as soon as the issue is resolved

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 131 Next › Last »