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.39
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 2 3 4 5 6 7 8 .. 131 Next › Last »

Kolaris commented on 2024-09-10 12:39 (UTC) (edited on 2024-09-10 12:39 (UTC) by Kolaris)

@Lone_Wolf I don't fully understand that, are you saying that having those packages installed while building llvm-minimal can cause problems? I was previously just asking if llvm needs to be built inside of the clean chroot like mesa

yurikoles commented on 2024-09-10 12:14 (UTC)

@adminion

Please read answers to your question carefully and avoid flooding.

adminion commented on 2024-09-10 11:42 (UTC)

@Lone_Wolf

can you fix this error in package?

mesa/meson.build:4:0: ERROR: Unknown options: "dri3, gallium-omx" A full log can be found at /var/tmp/pamac-build-user/mesa-git/src/_build/meson-logs/meson-log.txt ==> ERROR: A failure occurred in build(). Aborting...

adminion commented on 2024-09-10 11:41 (UTC)

@ArchUsr1 What does peru mean?

Lone_Wolf commented on 2024-09-10 10:00 (UTC)

@all : will look into building/updating in approx 9 hours when electric power is cheaper (for me).

@Billli11 : your answer is partially correct. repo mesa depends on repo llvm-libs which can be present when building llvm-minimal-git .

@Kolaris: If either of llvm , clang, compiler-rt from repos is installed, building llvm-minimal-git will cause problems. Having ocaml installed has a big chance of causing issues also.

Billli11 commented on 2024-09-10 00:53 (UTC)

@Kolaris It's depend on which llvm package is installed on your system, as mesa also depend on llvm at runtime.

Kolaris commented on 2024-09-09 23:32 (UTC)

I've been confused for a while regarding building this package with the first llvm option, so I have to ask. does llvm-minimal need to be built inside of the chroot as well? or can it be built outside then installed into the chroot to be used with mesa

ArchUsr1 commented on 2024-09-09 22:50 (UTC)

@adminion for now you have to manually delete dri3 and gallium-omx from PKGBUILD by doing paru -S --chroot mesa-git --fm vim or paru -S --chroot mesa-git --fm nano depending whether you use nano or vim for editing I hope maintainers will update this package soon.

adminion commented on 2024-09-09 22:37 (UTC) (edited on 2024-09-09 22:39 (UTC) by adminion)

==> Starting build()... The Meson build system Version: 1.5.1 Source dir: /var/tmp/pamac-build-user/mesa-git/src/mesa Build dir: /var/tmp/pamac-build-user/mesa-git/src/_build Build type: native build

mesa/meson.build:4:0: ERROR: Unknown options: "dri3, gallium-omx"

A full log can be found at /var/tmp/pamac-build-user/mesa-git/src/_build/meson-logs/meson-log.txt ==> ERROR: A failure occurred in build(). Aborting...

What I need to do?

Billli11 commented on 2024-09-09 19:27 (UTC) (edited on 2024-09-09 19:32 (UTC) by Billli11)

New MR !30865 just merged, mesa no longer have OMX frontend.
Add meson option gallium-omx has been removed.

Same as dri3, you'll need to remove the option to compile, and dependency libomxil-bellagio should no longer needed.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 131 Next › Last »