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.47
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 .. 27 28 29 30 31 32 33 34 35 36 37 .. 131 Next › Last »

Billli11 commented on 2022-02-08 17:30 (UTC)

clang, llvm, and llvm-libs has been updated from 13.0.0 to 13.0.1 in the official stable extra repositories.

Please update the PKGBUILD file.

Lone_Wolf commented on 2021-12-14 16:13 (UTC) (edited on 2021-12-14 16:14 (UTC) by Lone_Wolf)

nope, users should read the wiki before using any aur package.

Note: Packages in the AUR assume that the base-devel group is installed, i.e. they do not list the group's members as build dependencies explicitly.

See https://wiki.archlinux.org/title/Arch_User_Repository#Prerequisites

kmarius commented on 2021-12-14 14:54 (UTC)

bison, yacc and flex need to be added to makedepends.

zangoku commented on 2021-12-14 05:50 (UTC)

@rjahanbakhshi Thank you for your reply, manually building the package worked. Somehow it kept throwing errors with paru even when cleaning the cache.

rjahanbakhshi commented on 2021-12-14 01:56 (UTC)

@zangoku,
Have you tried to pull the latest changes? The patch has been removed from the PKGBUILD 5 days ago.

zangoku commented on 2021-12-13 23:27 (UTC)

No longer builds for me 

==> Starting prepare()...
Applying patch 0001-glx-fix-regression-for-drawable-type-detection.patch...
patching file src/glx/dri_common.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file src/glx/dri_common.c.rej
==> ERROR: A failure occurred in prepare().
    Aborting...
error: failed to build 'mesa-git-22.0.0_devel.147865.cdc480585c9.72594e4e5a9fbb575c2fce1a871bb4c9-1':

Lone_Wolf commented on 2021-12-08 09:48 (UTC)

@Devorlon

At buildtime a full llvm/clang tree is needed for mesa-git trunk , at runtime however only the libs pacakges are needed.

llvm-libs and llvm-libs-git conflict, and repo llvm requires llvm-libs . So llvm and llvm-git don't coexist, period .

Mesa-git can use 2 other llvm trunk builds that don't conflict with repo llvm-libs

  • my llvm-minimal-git / llvm-libs-minimal-git pacakge [1]

  • binary packages from Lordheavy's unofficial mesa-git repo[2] (for the sources he uses check [3] )

Keep in mind that llvm-git offers a complete development environment, but llvm-minimal-git and LH llvm-git don't .

[1] https://aur.archlinux.org/packages/llvm-minimal-git

[2] https://wiki.archlinux.org/title/Unofficial_user_repositories#mesa-git

[3] https://gitlab.com/lordheavy/mesa-git

Devorlon commented on 2021-12-08 01:13 (UTC) (edited on 2021-12-08 01:14 (UTC) by Devorlon)

It's probably been asked already, but is it OK to build llvm-git and mesa-git in a clean chroot and then install mesa-git outside of the chroot alongside llvm from extra?

Also, has anyone tried / would it be possible to compile with AOMP?

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 131 Next › Last »