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.38
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 .. 91 92 93 94 95 96 97 98 99 100 101 .. 131 Next › Last »

Krejzi commented on 2014-06-19 17:30 (UTC)

Hello, I maintain mesa-git package and it provides intel-dri-git too. I cannot upload a real split package because of this. Would you care to merge this package into mesa-git? Thanks.

Lone_Wolf commented on 2014-03-27 11:41 (UTC)

- changed from libclc-git to libclc as dependency - moved libomxil-bellagio to optdepends - switched from classic osmesa to gallium osmesa - enabled gallium tests

anadon commented on 2014-03-26 19:21 (UTC)

Everything works on my system without a hitch.

Lone_Wolf commented on 2014-03-25 11:43 (UTC)

that is correct, jpapadopoulos. I checked the mesa-git/libclc-git packagebuild and it does provide libclc . http://pkgbuild.com/~lcarlier/mesa-git/sources/libclc-git/PKGBUILD I'll change the dependency from libclc-git to libclc in next version. Then all that's needed to use either libclc-svn or libclc-git is for libclc-svn maintainer to add provides=('libclc') to the liblcl-svn PKGBUILD.

jpapadopoulos commented on 2014-03-25 11:28 (UTC)

There is an issue with building this without the mesa-git repo as a libclc-git PKGBUILD does not exist in AUR. There is only this package using svn(Apparently they use both) https://aur.archlinux.org/packages/libclc-svn/

Lone_Wolf commented on 2014-03-16 14:05 (UTC)

Patronmaster, check my answer in your thread here : https://bbs.archlinux.org/viewtopic.php?pid=1392795#p1392795 for reference (see below) i've just build the package again on my own system with makepkg, and have no conflict between clan-svn and llvm-svn (both from mesa-git repo). [panoramix@obelix mesa-r300-r600-radeonsi-git]$ makepkg ==> Making package: mesa-r300-r600-radeonsi-git 61886.7554539-2 (zo mrt 16 15:00:10 CET 2014) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Missing dependencies: -> llvm-svn -> libclc-git -> clang-svn ==> ERROR: Could not resolve all dependencies. [panoramix@obelix mesa-r300-r600-radeonsi-git]$ 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 LoneVVolf is up to date mesa-git is up to date :: Starting full system upgrade... there is nothing to do [panoramix@obelix mesa-r300-r600-radeonsi-git]$ sudo pacman -S llvm-svn libclc-git clang-svn resolving dependencies... looking for inter-conflicts... Packages (3): Name New Version Net Change mesa-git/clang-svn 204002-1 113.04 MiB mesa-git/libclc-git 116.20140315-1 10.27 MiB mesa-git/llvm-svn 204002-1 78.93 MiB Total Installed Size: 202.24 MiB :: Proceed with installation? [Y/n] (3/3) checking keys in keyring [#############################################] 100% (3/3) checking package integrity [#############################################] 100% (3/3) loading package files [#############################################] 100% (3/3) checking for file conflicts [#############################################] 100% (3/3) checking available disk space [#############################################] 100% (1/3) installing llvm-svn [#############################################] 100% (2/3) installing libclc-git [#############################################] 100% (3/3) installing clang-svn [#############################################] 100% [panoramix@obelix mesa-r300-r600-radeonsi-git]$ makepkg ==> Making package: mesa-r300-r600-radeonsi-git 61886.7554539-2 (zo mrt 16 15:01:18 CET 2014) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating mesa-r300-r600-radeonsi-git git repo... Fetching origin remote: Counting objects: 51, done. remote: Compressing objects: 100% (36/36), done. remote: Total 36 (delta 31), reused 0 (delta 0) Unpacking objects: 100% (36/36), done. From git://anongit.freedesktop.org./git/mesa/mesa 7554539..2e36116 master -> master -> Found LICENSE ==> Validating source files with md5sums... mesa-r300-r600-radeonsi-git ... Skipped LICENSE ... Passed ==> Extracting sources... -> Creating working copy of mesa git repo... Cloning into 'mesa-r300-r600-radeonsi-git'... done. Checking out files: 100% (4218/4218), done. Branch makepkg set up to track remote branch master from origin. Switched to a new branch 'makepkg' ==> Starting pkgver()... ==> Updated version: mesa-r300-r600-radeonsi-git 61891.2e36116-1 ==> Removing existing pkg/ directory... ==> Starting build()...

PatronMaster commented on 2014-03-15 17:57 (UTC)

Pacman -Q llvm-svn llvm-svn 202852-1 pacman -Q llvm-libs-svn llvm-libs-svn 202852-1 pacman -Q lib32-llvm-libs-svn lib32-llvm-libs-svn 202858-1 pacman -Q lib32-llvm-svn lib32-llvm-svn 202858-1 pacman -Q libclc-git libclc-git 116.20140304-1 All these packages are required to install: AUR mesa-r300-r600-radeonsi-git But it gave this error: In the :: clang-svn and llvm-svn are in conflict (llvm). Remove llvm-svn? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: lib32-llvm-svn: requires llvm-svn ==> WARNING: Your packages are saved in /tmp/yaourt-tmp-patron ==> Restart building mesa-r300-r600-radeonsi-git ? [y/N] ==> ---------------------------------------------------- ==> At the end of these packages had to be removed. First I need to install to run, then I have to remove.

Lone_Wolf commented on 2014-03-15 13:20 (UTC)

moved opencl related dependencies from depends to optdepends so they can be removed after building

Lone_Wolf commented on 2014-03-10 16:14 (UTC)

maybe you were thinking of this : OpenCL implementation from AMD is known as AMD APP SDK, formerly also known as AMD Stream SDK or ATi Stream. arch opencl wiki page has more info, but afaict AMD APP SDK allows the CPU to be used for opencl, NOT the graphics card.

lockheed commented on 2014-03-09 13:24 (UTC)

Thanks. But wasn't there something like "stream"? I read somewhere that thanks to it computations could be run on R600 cards.

« First ‹ Previous 1 .. 91 92 93 94 95 96 97 98 99 100 101 .. 131 Next › Last »