Package Details: mesa-git 25.0.0_devel.200442.bfa6b9b6551.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: rjahanbakhshi
Votes: 184
Popularity: 2.23
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-01-20 16:09 (UTC)

Required by (1334)

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 .. 51 52 53 54 55 56 57 58 59 60 61 .. 134 Next › Last »

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.

Terence commented on 2019-07-07 15:55 (UTC) (edited on 2019-07-07 15:58 (UTC) by Terence)

@Lone_Wolf Done: https://aur.archlinux.org/packages/libglvnd-glesv2.

Maybe add it as an optional dependency?

Lone_Wolf commented on 2019-07-07 11:42 (UTC)

@yurikoles

your first reply made clearer that aur helper users suffer from my choices, your 2nd reply is much closer to convincing me.

Atm the default setting for MESA_WHICH_LLVM doesn't match with the details shown in the AUR interface. Changing that is a good practice and benefits all users.

That this change benefits Aur helper users then becomes a bonus instead of the reason for the change. I'll upload a new version soon, probably monday.

Lone_Wolf commented on 2019-07-07 11:34 (UTC)

@zfkerr I'll correct mesa-vulkan-layer. As for gles packageconfig files : mesa devs feel that glvnd should provide those as glvnd builds that driver. I agree with them, and there's a patch available for glvnd that generates those files.

https://aur.archlinux.org/packages/mesa-git#comment-696495 Terence has a libglvnd package that includes the patch, maybe that could be uploaded to aur as a temporary solution ?

zfkerr commented on 2019-07-06 19:14 (UTC)

https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/mesa

@Lone_Wolf, mesa package in [extra] have glesv2.pc file, but your PKGBUILD haven't it. Please, add it too, because we have "mutter" package compilation issues without it.

And, please, replace "mesa-vulkan-layer" with "vulkan-mesa-layer" in the conflicts section in your PKGBUILD. "mesa-vulkan-layer" package does not exist! Thank you!

yurikoles commented on 2019-06-29 21:24 (UTC)

tl;dr:

Default choice .SRCINFO must be uploaded because it's default in PKGBUILD.

yurikoles commented on 2019-06-29 21:10 (UTC) (edited on 2019-06-29 21:13 (UTC) by yurikoles)

What benefit will makepkg & devtools users get if I unset the var before running printsrcinfo ?

I know that this is AUR helper again, but for example in yay there is --devel option which checks for new commits in git repo and updates package only if remote was updated. I also do understand that it seems to be irrelevant for llvm/mesa which land new commits frequently. But running single command that updates all packages automgically is better than to do all this cd <some-path> && git fetch -p && git reset --hard origin/master && makepkg -si for all packages manually. Because simple git pull will just fail in case of new version in AUR and fact that pkgver is dynamically updated in PKGBUILD file. So those AUR helpers really help.

In case of [lib32-]mesa-git this requires manual workaround to be involved like explicitly adding these packages to IgnorePkg, because in case of update yay automatically pulls llvm-git, which is stated in mesa-git .SRCINFO.

You may ask why not to use llvm-gitfrom [mesa-git] repo? In this case mesa-git is also pulled from this repo instead of AUR and only option is to first install some llvm-git binary package then disable this repo. And now we are in a loop, because we also need to IgnorePkg llvm-git which will be pulled from AUR in this case. [llvm-svn] repo is not an option, it's very outdated. So having mesa-git built from source requires also to rebuilding llvm-git all the time, because there is no [llvm-git] repo available with fresh version of llvm-git. And keeping old llvm-git build installed is worse than having stable version installed from official repo, because you lose not only stability, but also fresh new features in same time, because this build will be unstable and old in same time.

Lone_Wolf commented on 2019-06-29 19:40 (UTC)

by Yurikoles @Lone_Wolf Why don't you just generate it with MESA_WHICH_LLVM='' makepkg --printsrcinfo > .SRCINFO before uploading to AUR?

I could do that, but it looks to me as that will only benefit aur helpers users.

The way MESA_WHICH_LLVM works now is not a solution i'm proud of, but it does work fine with makepkg & devtools.

What benefit will makepkg & devtools users get if I unset the var before running printsrcinfo ?

Lone_Wolf commented on 2019-06-29 19:35 (UTC)

Thanks, bpierre and Haxk20

src/gallium/targets/opencl/meson.build file in mesa master has changed since the mesa MR was created, so I have created my own version.

« First ‹ Previous 1 .. 51 52 53 54 55 56 57 58 59 60 61 .. 134 Next › Last »