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

Dependencies (53)

Required by (1312)

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

Lone_Wolf commented on 2024-04-30 08:24 (UTC)

Confirmed, and you only need to add python-packaging .

@Reza : Due to changes in python 3.12 python-packaging is now a required makedepend . This package and it's lib32 counterpart both need it.

Grimish commented on 2024-04-29 21:53 (UTC)

Was getting a build error about python-mako version or something. Added python-setuptools to the deps list and it builds in a chroot.

Lone_Wolf commented on 2024-04-26 08:44 (UTC)

@kolaris :

it is possible to build this without llvm, but a lot of drivers will fail that way.

The only x86_64 ones I know of that will work without llvm are radv (vulkan-amd) and zink .

Since zink requires a working vulkan driver, that means only systems with a amd videocard can use this setup.

Kolaris commented on 2024-04-25 20:38 (UTC)

Is it possible to build this without using llvm? would that be a problem to do so? as in would it negatively impact performance or the other way around, etc...

ZephyrCheez commented on 2024-04-20 16:22 (UTC) (edited on 2024-04-20 16:35 (UTC) by ZephyrCheez)

Yeah, honestly I know this is supposed to be the "catch all" mesa package but honestly who in the heck is using Arch Linux WSL anyway? I don't think the D3D12 needs to be there, I think it can be its own package

Lone_Wolf commented on 2024-04-18 08:03 (UTC)

I doubt very much the gallium-d3d12 driver is used by vkd3d / vkd3d proton as they translate d3d to vulkan, not to some layer from MS.

Niinu commented on 2024-04-18 01:18 (UTC) (edited on 2024-04-18 14:56 (UTC) by Niinu)

vkd3d-proton support is nothing but niche... Edit: Yeah i just tested RE4 without the gallium-d3d12 driver and it seemed to run fine with vkd3d

ZephyrCheez commented on 2024-04-17 20:43 (UTC)

Since d3d12 gallium driver is only really necessary on a very niche use case, could it be removed from the PKGBUILD?

Billli11 commented on 2024-04-17 18:59 (UTC) (edited on 2024-04-17 19:02 (UTC) by Billli11)

@ArchUsr1

<h2>Overview</h2>

The D3D12 driver is a Gallium driver that emits API calls for Microsoft's :abbr:D3D12 (Direct3D 12) API instead of targeting a specific GPU architecture. This can be used to get full desktop OpenGL 3.3 support on devices that only support D3D12.

It's mainly use on WSL(Windows subsystem for Linux).
Not building it won't effect Linux PC.

ArchUsr1 commented on 2024-04-17 18:03 (UTC)

@charly2k24 I had to delete d3d12 and I'm using directx-headers-git. I'd like to know what's the proper fix for this because I'm not sure if it's used in some games.

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