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

Lone_Wolf commented on 2017-01-24 14:51 (UTC)

This is a VCS package that always builds the latest version and can never be out-of-date. Just try building it and you'll notice it builds a different version then the one listed above.

kerberizer commented on 2017-01-13 17:13 (UTC)

@Hi-Angel, depending on the case, direct replacing might also be possible, indeed. As for the "mesa is not a clone", this should occur only once. Subsequent builds should be fine.

Hi-Angel commented on 2017-01-13 17:08 (UTC)

@kerberizer thank you very much. I solved the dependencies by building lib32-test-mesa-git, and then installing both lib32-mesa-test-git and mesa-test-git at once. About "mesa is not a clone" — I did something similar, I just removed everything and rebuilt. But it's not a good solution in general, because it forces to build everything from scratch, instead of just changed sources.

kerberizer commented on 2017-01-13 14:23 (UTC)

@Hi-Angel, re breakings deps: Don't try simply removing the (lib32-)mesa-git packages. Instead, install the "stock" Arch's non-git Mesa packages, so that they __replace__ the -git ones. I.e. in lieu of "pacman -R lib32-mesa-git", do "pacman -S lib32-mesa". You might need to install several of Mesa (non-git) packages that way in order to fix the deps breaking. Once you're done with this, you can then replace those stock non-git packages with mesa-test-git. re mesa is not a clone: Simply remove the "mesa" subdirectory from the directory where the PKGBUILD resides and start makepkg again, letting it fetch the Mesa sources anew.

Hi-Angel commented on 2017-01-13 13:43 (UTC)

Well, now the problem is that I can't install the test mesa-git. Pacman complains: error: failed to prepare transaction (could not satisfy dependencies) :: lib32-mesa-git: removing mesa-git breaks dependency 'mesa-git' If I do sudo pacman -R lib32-mesa-git, it lists more packages to break, like lib32-cairo, which I don't want to remove. What do I do?

Hi-Angel commented on 2017-01-13 12:41 (UTC)

Hmm very odd. I just took the PKGBUILD not from testing, and I see the same error. But if I just put the snapshot into the empty dir, the error disappears, and mesa starts downloading.

Hi-Angel commented on 2017-01-13 12:29 (UTC)

Btw, while on it: what's the difference between "dri-drivers" and "gallium-drivers"? I'm just trying to convince myself whether I need a dri-driver "radeon", given I already have a gallium one "r600". FWIW, I always thought that nowadays radeon drivers are all using gallium API, so I'm confused.

Hi-Angel commented on 2017-01-13 12:21 (UTC)

Doesn't work for me, it says: ==> ERROR: /home/constantine/Projects/builds/mesa-git/mesa is not a clone of https://anongit.freedesktop.org/git/mesa/mesa.git Well, the directory is definitely not a clone of — sources are under "src/mesa" since the non-testing PKGBUILD.

Hi-Angel commented on 2017-01-13 12:07 (UTC)

You may probably want to remove everything *xvmc* from dependencies, given that you explicitly disabled it in autogen.

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 .

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