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 .. 33 34 35 36 37 38 39 40 41 42 43 .. 131 Next › Last »

rjahanbakhshi commented on 2021-04-13 15:38 (UTC) (edited on 2021-04-13 16:13 (UTC) by rjahanbakhshi)

@ekultails @Lone_Wolf

Enabling the virtio-experimental vulkan driver shouldn't affect any normal use cases and shouldn't have any negative side effects as far as I can tell. I have built it and checked if the icd driver exists and everything looks fine. The only minor annoyance is that it is experimental and we need to remove the flag in the future. I'm going to go ahead and enable virtio-experimental vulkan driver here.

For those who are interested to test this new driver, you're going to need to install the latest virglrenderer compiled with venus-experimental=true. I added a new AUR repo for that: https://aur.archlinux.org/packages/virglrenderer-git which you use. After updating mesa and virglrenderer, you can run tests using vtest on the same host by running virgl_test_server --venus in the background and setting the following environment variables before running your application. 

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/virtio_icd.x86_64.json 
VN_DEBUG=all

For example: 

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/virtio_icd.x86_64.json VN_DEBUG=all vulkaninfo

Or using vulkan demos from https://github.com/SaschaWillems/Vulkan 

git clone --recursive https://github.com/SaschaWillems/Vulkan.git
cd Vulkan
git submodule init
git submodule update
python download_assets.py
mkdir build
cd build
cmake ..
make
cd bin
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/virtio_icd.x86_64.json VN_DEBUG=all ./gears

And you should be able to see the gears or other demos using this driver.

Furthermore, to use this driver from qemu you're gonna need the VIRTIO_GPU_F_CONTEXT_INIT in the kernel which can be found here https://gitlab.freedesktop.org/virgl/drm-misc-next/-/commits/context-init/ also support for VIRTIO_GPU_F_RESOURCE_BLOB by qemu which isn't available at the moment.

shoober420 commented on 2021-04-13 12:01 (UTC)

@theriddick

Do you have a custom repo added that would include mesa-git like chaotic-aur or the mesa-git repo?

Lone_Wolf commented on 2021-04-13 10:49 (UTC)

theriddick, that sounds like your local PKGBUILD is not the latest one.

run git pull in your build folder to ensure you start with the most recent uploaded version.

llvm 11.1.0 is the latest released version and should be in manjaro repos. Use pacman -Ss llvm to verify .

If that doesn't list llvm 11.1.0 there's something wrong with manjaro repos.

theriddick commented on 2021-04-13 03:10 (UTC) (edited on 2021-04-13 03:12 (UTC) by theriddick)

I don't know why but on my manjaro system pamac gets super confused with this package, it claims this is infact the normal repo version (-git) and also same issue with lib32-mesa-git.. As such it claims that it needs llvm 11.0.1 which is not available in standard packages.

Basically pamac can't identify between official and aur repo of this package. Also YAY has this same issue and needs -a flag to install the AUR version.

Just going to try and blacklist mesa-git and lib32-mesa-git and see if that fixes it... MESA_WHICH_LLVM is set to 4 (11.1)

Lone_Wolf commented on 2021-04-09 09:56 (UTC) (edited on 2021-04-09 09:58 (UTC) by Lone_Wolf)

We'll look into it, ekultails .

TkG, could you look at this new option and email me and reza about upsides / downsides ?

LukeShortCloud commented on 2021-04-09 03:39 (UTC)

VirtIO Vulkan support was added today (2021-04-08) and requires an additional flag. [1] Would it be possible to add it to the PKGBUILD?

-Dvulkan-drivers=virtio-experimental

  1. https://lists.freedesktop.org/archives/mesa-dev/2021-April/225036.html

rjahanbakhshi commented on 2021-03-27 17:06 (UTC)

PKGBUILD updated to reflect the change in meson vulkan-layers options. Also the wrong commit from the last night has been reverted.

<deleted-account> commented on 2021-02-25 02:59 (UTC)

I can addopt this pakage! @Lone_Wolf

Here is the link were I have my PKGBUILD : https://github.com/kevall474/Mesa/tree/master/mesa-git

rjahanbakhshi commented on 2021-02-24 08:22 (UTC)

0001-clover-llvm13-use-FixedVectorType.patch is missing a semicolon in the #else clause.

Thanks for reporting the issue. It's been fixed now.

« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 .. 131 Next › Last »