Package Details: mesa-git 25.2.0_devel.204321.de6efc01c12.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: rjahanbakhshi
Votes: 188
Popularity: 2.00
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2025-04-16 20:46 (UTC)

Dependencies (52)

Required by (1331)

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 .. 41 42 43 44 45 46 47 48 49 50 51 .. 134 Next › Last »

sinatosk commented on 2020-08-25 07:45 (UTC)

artivision

zink is already enabled in mesa-git and lib32-mesa-git, you just need to re-install them as it does a git checkout of the latest changes from where the mesa source code is hosted at

artivision commented on 2020-08-24 23:47 (UTC)

Good day. Does this build provide Zink OGL 4.6 patches?

bobberb commented on 2020-07-27 19:21 (UTC)

Dear Lone_Wolf,

llvm-libs and lib32-llvm-libs are now at 10.0.1-1

sinatosk commented on 2020-07-24 15:55 (UTC)

For people who don't know, instead of using Option A or Option B stated by Lone_Wolf

you can instead use the following command

sudo pacman -Syu llvm-libs lib32-llvm-libs --assume-installed llvm-libs=10.0.0,lib32-llvm-libs=10.0.0

This is basically telling pacman that you "virtually" have llvm-libs and lib32-llvm-libs 10.0.0 ( set these two version numbers on the command above to the versions matched with your currently installed llvm-libs and lib32-llvm-libs ), then the command will upgrade your system as usual

then you can recompile mesa-git and lib32-mesa-git against again

maybe add this as an Option C Lone_Wolf?

Lone_Wolf commented on 2020-07-11 16:11 (UTC)

Those asserts are supposed to be useful for debugging but hinder performance. When buildtype is Release they're disabled always.

Archlinux has build mesa with b_ndebug=true since we switched from autotools meson / ninja for building it.

The upstream gcc bug is at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96130

Maybe gcc devs find a solution fast, if not reverting the mesa commit that triggered this may be an option.

jpapadopoulos commented on 2020-07-11 11:20 (UTC) (edited on 2020-07-11 12:47 (UTC) by jpapadopoulos)

GCC bug affecting building Mesa from git https://gitlab.freedesktop.org/mesa/mesa/-/issues/3242 https://bugs.archlinux.org/task/67229

It appears to build if ndebug is set to false as mentioned in the Mesa report. If I'm understanding this correctly, setting it to false enables std C assertions and negatively affects performance?

Lone_Wolf commented on 2020-07-02 14:45 (UTC)

Both archlinux and mesa bugtrackers don't show LTO related problems with mesa afaik.

Re-enabled LTO.

Lone_Wolf commented on 2020-06-23 11:29 (UTC)

Yup, removed the relevant commands.

phush0 commented on 2020-06-23 07:53 (UTC) (edited on 2020-06-23 07:57 (UTC) by phush0) 

ninja: Entering directory `_build'
ninja: error: unknown target 'xmlpool-pot'

It will not build

Edit: It seem changed translation facilities in patch 2ef983dca61b549a9242afd9008200b231a26e90

Lone_Wolf commented on 2020-06-02 14:17 (UTC) (edited on 2020-06-02 14:19 (UTC) by Lone_Wolf)

Yes, this is a side effect of my request to increase the minimum meson version https://gitlab.freedesktop.org/mesa/mesa/-/issues/2737 .

I'll look into updating the meson options, hopefully this week.

Edit : enabling LTO did increase built time considerably. While it decreased the size of the binaries, I'm not sure of performance benefits. For now i'm keeping it disabled.

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 134 Next › Last »