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.41
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 .. 45 46 47 48 49 50 51 52 53 54 55 .. 131 Next › Last »

Snoop05 commented on 2019-10-28 12:56 (UTC) (edited on 2019-10-28 12:56 (UTC) by Snoop05)

Please add zink to the list of gallium drivers since it got merged.

https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2363

Lone_Wolf commented on 2019-10-26 16:52 (UTC)

The (incorrect) increase in installed size is discussed at https://bugs.archlinux.org/task/64252

Lone_Wolf commented on 2019-10-26 10:38 (UTC) (edited on 2019-10-26 10:45 (UTC) by Lone_Wolf)

No weird things with pacman 5.2 using xz compression except total installed size seems off. glxinfo & firefox work. I don't use steam, so can't test that.

$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 lonewolf                                                        6.6 KiB  0.00   B/s 00:00 [####################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (1)        Old Version                        New Version                        Net Change  Download Size

lonewolf/mesa-git  19.3.0_devel.116650.6b166d6fb1c-1  19.3.0_devel.116763.ace5138548c-1    0.28 MiB      35.30 MiB

Total Download Size:    35.30 MiB
Total Installed Size:  391.72 MiB
Net Upgrade Size:        0.28 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 mesa-git-19.3.0_devel.116763.ace5138548c-1-x86_64              35.3 MiB  1535 MiB/s 00:00 [####################################################] 100%
(1/1) checking keys in keyring                                                             [####################################################] 100%
(1/1) checking package integrity                                                           [####################################################] 100%
(1/1) loading package files                                                                [####################################################] 100%
(1/1) checking for file conflicts                                                          [####################################################] 100%
(1/1) checking available disk space                                                        [####################################################] 100%
:: Processing package changes...
(1/1) upgrading mesa-git                                                                   [####################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
$

Haxk20 commented on 2019-10-25 17:20 (UTC) (edited on 2019-10-25 18:21 (UTC) by Haxk20)

WRONG ASSUMPTION. I just built at wrong time. Its now fixed in master. But the huge update size still stays so yeah. 260mb update isnt nice. Pacman 5.2 broke mesa-git kind of. Steam seg faults with mesa-git when installed with pacman 5.2 for some reason. The package update is 250mb bigger then it should be (Package size is normal. Just when installing it says its 250mb bigger). I guess compression is broken.

Lone_Wolf commented on 2019-10-24 11:44 (UTC)

*-git packages always retrieve the latest available commits from their sources and adjust pkgver to reflect that at build time. They are never out of date and only updated when changes in the PKGBUILD are required.

Lone_Wolf commented on 2019-10-17 23:11 (UTC)

Popolon, try with mesa-git and https://aur.archlinux.org/packages/libglvnd-glesv2/

Popolon commented on 2019-10-17 16:55 (UTC)

There is a problem with OpenGL detection on cmake, when using this package (tested with makepkg on olive(aur), works fine with default(extra) mesa 

CMake Error at /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find OpenGL (missing: OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.15/Modules/FindOpenGL.cmake:397 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:22 (find_package)

Lone_Wolf commented on 2019-10-16 12:11 (UTC) (edited on 2019-10-16 12:12 (UTC) by Lone_Wolf)

Both mesa-git & lib32-mesa-git have been updated to depend on llvm 9.

Thanks for the alert, xdavidwu

xdavidwu commented on 2019-10-15 14:54 (UTC)

extra/llvm has been updated to 9.0.0 and the PKGBUILD needs to be updated for building with it (lib32-mesa-git also has the same problem)

==> Installing missing dependencies...
error: target not found: llvm-libs=8.0.1
==> ERROR: 'pacman' failed to install missing dependencies.

aufkrawall commented on 2019-10-14 14:55 (UTC)

@Lone_Wolf Yes, it successfully builds with mesa and libglvnd from regular repository. However, Firefox on XWayland silently falls back to non-OGL rendering, so there seems to be soemthing wrong apart from that. Highly confusing situation...

« First ‹ Previous 1 .. 45 46 47 48 49 50 51 52 53 54 55 .. 131 Next › Last »