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

Dependencies (53)

Required by (1315)

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 .. 101 102 103 104 105 106 107 108 109 110 111 .. 131 Next › Last »

<deleted-account> commented on 2013-07-12 10:19 (UTC)

@klausenbusk ok! sorry! :D

<deleted-account> commented on 2013-07-11 19:42 (UTC)

@oriolj taken from Arch's wiki: Packages in the AUR assume the base-devel group is installed, and AUR packages will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds.

<deleted-account> commented on 2013-07-11 18:15 (UTC)

Hi! we should add as makedepends: libtool bison flex

<deleted-account> commented on 2013-07-05 23:12 (UTC)

arh, I added 'llvm>=3.0' just after llvm 3.3 have got into extra, stupid typing mistake :) Fixed now.. 5 min, and linking is enabled..

Krejzi commented on 2013-07-05 22:36 (UTC)

This is wrong: 'llvm>=3.0'. As I said, you need 3.3 at least. My initial question was to ask you to enable linking to llvm shared libs as the package in [extra] does.

<deleted-account> commented on 2013-07-05 22:34 (UTC)

I'm confused, what you want me to do? mesa-git already depends on llvm (not llvm-amdgput-snapshot).

Krejzi commented on 2013-07-05 21:58 (UTC)

Mesa 9.2 git snapshot depends on LLVM revision 181269 and later, which is now essentialy LLVM 3.3. http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/radeon/LLVM_REVISION.txt Mesa 9.1 can't be used with LLVM 3.3 (without backporting the patches) and needs llvm-amdgpu-snapshot which was "stabilized" for 9.1. You are right that mesa works with version of llvm it was built against, but only major version which happens every 6 months and I think if someone builds mesa-git every lets say 6.5 months or so shouldn't really use it :). As for OpenCL, no problem. It was just a suggestion.

<deleted-account> commented on 2013-07-05 21:46 (UTC)

@Krejzi mesa in extra depends on llvm-amdgpu-snapshot. The problem is mesa only work with that version of LLVM it is built with (correct me if I'm wrong..), which could cause mesa to crash when LLVM get updated in extra.. About OpenCL, I think no. Most people don't need or use OpenCL and those who do can easily add it itself. That just what is think..

Krejzi commented on 2013-07-05 18:19 (UTC)

Why don't you just depend on llvm 3.3 and enable llvm shared libs as it's done in 9.1 in [extra]? With static llvm some segfaults are happening. Also, is it a problem if you mention libclc dependency and --enable-opencl switch for r600/radeonsi OpenCL support? It should be noted that it provides/conflicts with libcl and opencl-headers from the offical repos.

<deleted-account> commented on 2013-06-19 14:48 (UTC)

@LEW21, thanks :) Updated package with needed fix to get version number, and depends on llvm=>3.0 instant of llvm-amdgpu.. thing.

« First ‹ Previous 1 .. 101 102 103 104 105 106 107 108 109 110 111 .. 131 Next › Last »