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 .. 72 73 74 75 76 77 78 79 80 81 82 .. 131 Next › Last »

Lone_Wolf commented on 2016-12-28 13:01 (UTC)

sthalik, no build issues here. Check these : Are base-devel and/or multilib-devel (only needed for building lib32-* stuff) installed ? have you run pacman -Syu just before building ? Is your building folder on a native linux filesystem ? If those checks all succeed, post full build log on a pastebin site. As for building against stable llvm/clang : check my comment from 2016-20-12 .

sthalik commented on 2016-12-27 13:38 (UTC)

Also mesa no longer requires llvm-svn and can do with regular llvm. I solved it locally with dummy *-svn packages. Gallium builds as it should.

sthalik commented on 2016-12-27 13:37 (UTC)

Without manual `git config core.symlinks true' the build fails on r200. Please set symlink support in the source repository.

talonz commented on 2016-12-23 20:25 (UTC)

thanks wolf, testing it out now

Lone_Wolf commented on 2016-12-20 12:26 (UTC)

Mesa trunk Master follows llvm/clang svn closely. By building mesa-git against stable llvm/clang versions you may gain some stability, but will miss out on the latest features. ex : mesa-git + llvm 3.9.0 will report OpenGL 4.3 for radeonsi driver, not OpenGL 4.5 as it reports with llvm-svn . For the sake of argument, let's assume that is acceptable and mesa-git would switch to depending on llvm/clang . For building in a clean chroot the way pacman resolves dependencies would result in mesa-git being build against llvm/clang from extra repo. Those that wanted to do a clean chrootbuild against llvm-svn/clang-svn would have to use a custom pacman.conf for the chroot or change the PKGBUILD. Bugs occurring with mesa-git + stable llvm/clang would often get : 'switch to latest llvm-svn/clang-svn" as response. There are many more pitfalls. TL;DR : building mesa-git against stable llvm/clang is tecnically possible, but opens a big can of worms.

dreieck commented on 2016-12-20 07:06 (UTC) (edited on 2016-12-20 07:07 (UTC) by dreieck)

Does this package really need clang-svn to build? Does clang not suffice? The same with llvm: Does it really need llvm-svn to build, does llvm not suffice? For me, I did build it with "llvm" and "clang". So, would be good to include just those as build deps (the -svn-variants should provide the non-svn-variants).

Lone_Wolf commented on 2016-12-18 15:55 (UTC)

I am working on a simpler package, you can find it here : https://aur.archlinux.org/packages/mesa-test-git/ Please help to test it.

Lone_Wolf commented on 2016-12-18 15:54 (UTC)

The lib32 companion package is now also uploaded : https://aur.archlinux.org/packages/lib32-mesa-test-git/

Lone_Wolf commented on 2016-12-11 23:46 (UTC) (edited on 2016-12-11 23:46 (UTC) by Lone_Wolf)

This package is similar to my mesa-git package, but : - has only 2 sub packages instead of 7 - is less work to maintain - cleaner PKGBUILD - installs everything build (mesa-git & stock mesa don't use all files build ) The configure flags have also changed somewhat. Once this has had enough testing I intend to merge this into mesa-git .

Lone_Wolf commented on 2016-12-10 12:24 (UTC)

Strunkenbold, aig : Thanksfor the reports. Stock mesa 13.0.2-1 changed interaction of vulkan related packages, 13.02-2 did same for opencl packages. I'll adjust things this weekend.

« First ‹ Previous 1 .. 72 73 74 75 76 77 78 79 80 81 82 .. 131 Next › Last »