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

Dependencies (53)

Required by (1272)

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 .. 122 123 124 125 126 127 128 129 130 131 Next › Last »

LinuxDonald commented on 2011-05-17 02:10 (UTC)

How can i enable libtxc_dxtn support?

tavianator commented on 2011-05-15 23:42 (UTC)

@gloriole: Have you read the PKGBUILD? Uncomment the split pkgname= line and all is fixed. Clearly libgl-git makes no sense as a makedepend, since this package builds it. I'm uploading a new PKGBUILD that fixes the license directories now though, thanks.

<deleted-account> commented on 2011-05-15 21:44 (UTC)

The following lines from Yaourt (Y/N prompts were answered with the default): ==> Continue installing mesa-git ? [Y/n] ==> [v]iew package contents [c]heck package with namcap ==> --------------------------------------------------- ==> c mesa-git E: Missing custom license directory (usr/share/licenses/mesa-git) mesa-git E: Dependency libgl detected and not included (libraries ['usr/lib/libGL.so.1'] needed in files ['usr/lib/libGLU.so.1.3.071100', 'usr/lib/libGLw.so.1.0.0']) mesa-git W: Dependency included and not needed ('libgl-git') mesa-git W: Dependency libx11 included but already satisfied mesa-git W: Dependency gcc-libs included but already satisfied mesa-git W: Dependency included and not needed ('dri2proto-git') mesa-git W: Dependency included and not needed ('libdrm-git') mesa-git W: Dependency included and not needed ('glproto-git') ==> Continue installing mesa-git ? [Y/n] ==> [v]iew package contents [c]heck package with namcap ==> --------------------------------------------------- ==> Password: resolving dependencies... warning: cannot resolve "libgl-git", a dependency of "mesa-git" :: The following package cannot be upgraded due to unresolvable dependencies: mesa-git Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: mesa-git: requires libgl-git ==> WARNING: Following packages have not been installed: mesa-git $

<deleted-account> commented on 2011-05-15 18:47 (UTC)

$ namcap aur-mesa-git/PKGBUILD PKGBUILD (mesa-git) E: Split PKGBUILD needs additional makedepends ['libgl-git'] to work properly

tavianator commented on 2011-05-13 16:42 (UTC)

Hmm? I'm not sure what you're getting at. Anyway I've uploaded an updated PKGBUILD.

esterun commented on 2011-05-13 12:00 (UTC)

here ? →package_libgles-git() { depends=('libgl-git') conflicts=('libgles') provides=("libgles=${_mesaver}") pkgdesc="Mesa GLES libraries and headers" WTF problème ? :(

esterun commented on 2011-05-13 11:59 (UTC)

add → libgl-git to makedeps ? At the end he ask about it, i dont know if it's realy important...

tavianator commented on 2011-04-16 00:06 (UTC)

@fawek: No other git package does that, and the fact that the git repo has history has come in handy for me occasionally, so I'm keeping it as is. Feel free to add --depth=1 locally if you want, but after you do the first fetch, subsequent ones will be very small anyway. @Huulivoide/LinuxDonald: I'll add that as the default soon, no need for the prompt.

<deleted-account> commented on 2011-04-15 21:22 (UTC)

It might be a good idea to add --depth 1 to the git command in PKGBUILD so as to reduce the number of objects being pulled from the repository to the necessary minimum.

Huulivoide commented on 2011-04-15 18:07 (UTC)

Floating point texture support has been merged to mainline, and canbe found under --enable-texture-float swich. As this is patended feature not everyone will want it. But could you add something like: echo "Do you want to enable patented features? y/n" read answer if [[ "$answer" == "y" ]]; then patented="--enable-texture-float"; fi ... configure ... $patented so that people could easily enable it and get info that it exist in there :D