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

Required by (1305)

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 .. 89 90 91 92 93 94 95 96 97 98 99 .. 131 Next › Last »

Scimmia commented on 2014-07-27 16:04 (UTC)

It's only too specific if the dep requires a specific version (=). If it's greater than or less than, using $pkgver should work fine. I can't think of a situation where someone would need that specific of a version of mesa.

kerberizer commented on 2014-07-27 15:46 (UTC)

@Scimmia: My guess is that it's because pkgver() is too specific to be really useful for the dependency (provides/depends) stuff. I've been having the same problem with my own archzfs-git PKGBUILDs and was thinking about a similar solution.

Scimmia commented on 2014-07-27 15:33 (UTC)

Ah, I gotcha, I had just noticed the "provides" on this page, which just shows 'mesa='. Still, why not just use $pkgver? Seems redundant.

kerberizer commented on 2014-07-27 14:37 (UTC)

@Scimmia, _mesaver is a function, not a variable. $(_mesaver) is replaced by the output of that function. _mesaver() { path="${srcdir}/mesa/VERSION" [ -f $path ] && cat "$path" }

Scimmia commented on 2014-07-27 14:14 (UTC)

You're using paren around the _mesaver variable, which is wrong and doesn't work. They should either be curly brackets or simply removed.

shoober420 commented on 2014-07-23 10:29 (UTC)

@kerberizer: My bad, I had no idea how the AUR -git packages work. It truly is amazing. It seriously can't get any better then being able to go directly to the git and update yourself. Arch is fricking awesome.

kerberizer commented on 2014-07-23 09:53 (UTC)

@shoober420: But this is just a PKGBUILD, not a binary package -- if you are referring to the Ubuntu PPAs -- and it's based on the master branch of Mesa's Git repo. So, each time you do build a package using it, you get the latest possible code. For example, I go as far as rebuilding daily, especially if I spot interesting new commits in the repo. The date here, 2014-06-29, reflects only when the PKGBUILD itself has been updated, and it shouldn't need updating unless the build process breaks due to changes "upstream". Or am I missing the point here?

mmstick commented on 2014-06-29 07:56 (UTC)

It's certainly fixed now. Thanks.

« First ‹ Previous 1 .. 89 90 91 92 93 94 95 96 97 98 99 .. 131 Next › Last »