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.39
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 .. 69 70 71 72 73 74 75 76 77 78 79 .. 131 Next › Last »

Lone_Wolf commented on 2017-03-11 17:29 (UTC)

I have looked into building aur mesa-git with libglvnd support, but the patches used in stock mesa 17.0.1-2 don't apply cleanly to git master . For now aur mesa-git is sticking to the mesa-libgl symlink method. Users that combine nvidia driver with this package may encounter problems.

Shugyousha commented on 2017-03-11 13:41 (UTC)

I get an unresolvable conflict with libglvnd when trying to mesa-git: sudo pacman -U mesa-git-17.1.0_devel.89730.3d253d330a-1-x86_64.pkg.tar.xz mesa-libgl-git-17.1.0_devel.89730.3d253d330a-1-x86_64.pkg.tar.xz loading packages... resolving dependencies... looking for conflicting packages... :: mesa-git and mesa are in conflict. Remove mesa? [y/N] y :: mesa-libgl-git and libglvnd are in conflict (libgles). Remove libglvnd? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: lib32-libglvnd: removing libglvnd breaks dependency 'libglvnd' I could not find a way to solve this because mesa-git does not provide lbglvnd but does seem to conflict with it (and there are a lot of packages depending on libglvnd). Am I missing something obvious?

Lone_Wolf commented on 2017-03-11 12:21 (UTC)

Haagch, are you sure this package is still needed now both intel and radeon vulkan support is integrated in mesa ?

Lone_Wolf commented on 2017-03-11 12:17 (UTC)

@jugs : kerberizer is correct. comment deleted.

kerberizer commented on 2017-03-11 04:19 (UTC)

@jugs, that comment was made before the packages were merged, so it was actually imported from the mesa-test-git and Lone_Wolf did make it there. I suppose he'll delete it now that the packages are already merged and mesa-test-git is no more.

jugs commented on 2017-03-11 04:15 (UTC)

Switch back to mesa-git? Isn't this mesa-git?

Lone_Wolf commented on 2017-02-27 22:58 (UTC)

migrated to scheme used in mesa-test-git. If you also have lib32-mesa-git or lib32-mesa-test-git version installed, pacman will report a conflict. The easiest solution is to revert lib32-* to stock lib32-mesa . pacman will then allow installing mesa-git and you can build/install lib32-mesa-git.

kerberizer commented on 2017-02-19 14:55 (UTC)

@DiFuzZzoR, keep also in mind this: https://www.archlinux.org/news/phasing-out-i686-support/

Lone_Wolf commented on 2017-02-19 13:05 (UTC)

DiFuzZzoR, if you need multilib 32-bit packages, like for wine & skype , check lib32-mesa-test-* . In case you are referring to native i686 : if people are willing to test mesa trunk on systems running i686 archlinux , i'm willing to adjust the package.

« First ‹ Previous 1 .. 69 70 71 72 73 74 75 76 77 78 79 .. 131 Next › Last »