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

Dependencies (53)

Required by (1301)

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

Lone_Wolf commented on 2017-05-27 23:17 (UTC)

Thanks for the report, Gelmo . It appears to be a mesa bug, i created https://bugs.freedesktop.org/show_bug.cgi?id=101214 . Those who want to build mesa git master without libglvnd support can use the last version (just 6 days old) without libglvnd support : https://aur.archlinux.org/cgit/aur.git/tree/?h=mesa-git&id=ded28cf3ae8ba334bca3081755229ec42b24a170

Gelmo commented on 2017-05-27 06:42 (UTC)

I'm on Manjaro 4.12rc, and xdriinfo wasn't finding radeonsi with libglvnd on my system. I removed the glvnd dependency and patches, and commented out the switch to enable it, and it worked without a problem. If other people need this, I'll make a package, but it's simple enough. I'm not on Arch so I probably shouldn't be maintaining a pkg.

Lone_Wolf commented on 2017-05-22 15:09 (UTC)

Package is now build with glvnd support. Before building : install https://aur.archlinux.org/packages/dummy-opengl-driver-git/ (can be removed afterwards) When building outside a chroot, install libglvnd manually. If you don't, makepkg -s and -r options are likely to fail due to conflicts.

yurikoles commented on 2017-03-17 04:22 (UTC)

sandy8925, this package replaces most of mesa-related packages, see "replaces" verb in PKGBUILD

sandy8925 commented on 2017-03-17 04:19 (UTC)

Hello, it looks like following packages: libva-mesa-driver, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-radeon are now separate, and are not built as part of mesa. So, when I build mesa-git, none of the above package files are created like they were previously, and there are no -git versions of these packages in AUR. Are these files part of the mesa-git package that gets created? How does this work?

Lone_Wolf commented on 2017-03-15 14:18 (UTC)

WARNING - MANUAL ACTION NEEDED Mesa devs informed me that the server(s) hosting mesa trunk code are having trouble with the amount of work needed for git over http/https traffic and asked if i could switch back to git:// protocol. I have changed the source uri. On your next build makepkg will complain that the existing sourcefolder is not a valid clone. cd into the folder where makepkg stores downloaded sourcefiles (it should have a folder called branches) . run " git remote -v " origin https://anongit.freedesktop.org/git/mesa/mesa.git (fetch) origin https://anongit.freedesktop.org/git/mesa/mesa.git (push) If your output differs, you're in wrong folder. run " git remote set-url origin git://anongit.freedesktop.org/mesa/mesa " run " git remote -v " again origin git://anongit.freedesktop.org/mesa/mesa (fetch) origin git://anongit.freedesktop.org/mesa/mesa (push) Now makepkg will no longer complain.

Lone_Wolf commented on 2017-03-14 22:43 (UTC)

Thanks for the heads up , yurikoles . patch removed.

yurikoles commented on 2017-03-14 15:27 (UTC)

Seems like disable-pthread-stubs-on-linux.patch is no longer needed since this commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=b82bd31c54cc91b972a027492fa75b13cd9c7267

Shugyousha commented on 2017-03-11 18:09 (UTC)

@Lone_Wolf: thanks, that did the trick! I knew that I would have to replace both lib32-mesa & mesa with their git counterparts at the same time but since the lib32-mesa-git depends on mesa-git which couldn't be installed, I did not manage to do it. Ignoring dependencies with the -dd switch is something I would not recommend but in this case I don't think there was another way and it worked without a problem, thanks!

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

@Shugyousha : you will have to replace lib32-mesa & mesa with their git counterparts at the same time. If you build in a clean chroot this is a bit tricky, but doable. If you build on a running system, use pacman -Rdd to remove all lib32-mesa-* parts you have installed. After you have build & installed mesa-git, you can then build and install lib32-meas-git.

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