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

Dependencies (53)

Required by (1302)

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

OroWith2Os commented on 2022-11-26 03:48 (UTC)

Mesa builds are broken on my end because of the --no-pager Meson option inside of build().

My system is fully up-to-date.

I have confirmed that removing --no-pager works to fix the build error.

deemon commented on 2022-11-14 21:56 (UTC)

Ah I see. I am using Manjaro and pacman -Syu didn't fetch anything new yesterday. However, we got some stable release today and after installing that, AUR mesa-git also builds and got installed :)

Lone_Wolf commented on 2022-11-13 21:13 (UTC) (edited on 2022-11-13 21:14 (UTC) by Lone_Wolf)

from meson 0.64.0 release notes :

Pager and colors for meson configure output

The output of meson configure, printing all options, is now more readable by automatically using a pager (less by default) and colors. The pager used can be controlled by setting PAGER environment variable, or --no-pager command line option.

run pacman -Syu before building

fezzik commented on 2022-11-13 21:09 (UTC)

Fails to build with: vulkan-intel-git/src/fakeinstall/usr/local/include/vulkan/vulkan_intel.h': No such file or directory

deemon commented on 2022-11-13 21:03 (UTC) (edited on 2022-11-13 21:04 (UTC) by deemon) 

meson: error: unrecognized arguments: --no-pager
==> ERROR: A failure occurred in build().
    Aborting...

<deleted-account> commented on 2022-10-27 13:23 (UTC)

@rjahanbakhshi thanks for the reply. Yeah, I decided to go ahead with the installation, and simply replaced them with -git version when prompted, and it worked.

mesa-git and lib32-mesa-git installed successfully.

rjahanbakhshi commented on 2022-10-25 09:09 (UTC)

@Smokus,

I'm not familiar with yay but those conflicting packages, namely vulkan-radeon, libva-mesa-driver, mesa-vdpau, mesa (mesa-libgl), are all provided by mesa-git package itself. When installing mesa-git, all those conflicting packages should be uninstalled. Using PKGBUILD will take care of installation and uninstallation. Yay should do the same.

<deleted-account> commented on 2022-10-22 12:24 (UTC)

I currently use mesa from official Extra repo. I want to install this AUR mesa-git package.

All that I need to do is to run yay -S mesa-git lib32-mesa-git or do I need to do something else as well?

I am asking because when I run only yay -S mesa-git I get the following output in Terminal:

Package conflicts found:
 -> Installing mesa-git will remove: mesa, vulkan-radeon, libva-mesa-driver, mesa-vdpau, mesa (mesa-libgl)
 -> Conflicting packages will have to be confirmed manually

rjahanbakhshi commented on 2022-10-01 15:30 (UTC) (edited on 2022-10-01 15:32 (UTC) by rjahanbakhshi)

@Cloudperry, @schlunze

Thanks for the report. xvmc is removed upstream. See here https://gitlab.freedesktop.org/mesa/mesa/-/commit/8cc766d8f7eac26b7c029a2fac1bdfdba4776c29

PKGBUILD updated to address the upstream change.

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

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