Package Details: mesa-git 19.2.0_devel.111394.d68218dbca9-1

Git Clone URL: https://aur.archlinux.org/mesa-git.git (read-only)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL: https://www.mesa3d.org
Keywords: mesa X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-radeon
Provides: libva-mesa-driver=19.2.0_devel.111394.d68218dbca9-1, mesa=19.2.0_devel.111394.d68218dbca9-1, mesa-vdpau=19.2.0_devel.111394.d68218dbca9-1, opencl-driver, opencl-mesa=19.2.0_devel.111394.d68218dbca9-1, opengl-driver, vulkan-driver=19.2.0_devel.111394.d68218dbca9-1, vulkan-intel=19.2.0_devel.111394.d68218dbca9-1, vulkan-radeon=19.2.0_devel.111394.d68218dbca9-1
Submitter: Krejzi
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 157
Popularity: 1.700027
First Submitted: 2014-06-19 21:33
Last Updated: 2019-06-04 14:33

Required by (889)

Sources (2)

Pinned Comments

Lone_Wolf commented on 2019-06-04 15:15

AUR Helpers are NOT supported

I built and test with makepkg. Building with Devtools and Clean Chroot Manager should work fine also (I test them occasionally).

This package and lib32-mesa-git use a custom method to dynamically determine which llvm version is to be used. Several AUR helpers (atleast pamac and yay) can't handle that method.

Incase you try to build mesa-git with one of those AUR helpers, run makepkg --printsrcinfo > .SRCINFO after downloading and BEFORE building.

That should help pamac and yay to handle my custom method.

Lone_Wolf commented on 2019-05-09 13:30

This package now uses an environment variable to determine which llvm package it will be built against. Check PKGBUILD for details.

Lone_Wolf commented on 2018-01-30 14:06

  • issues
Simple issues can be dealth with through aur comments, but sometimes discussion is needed.
Use https://bbs.archlinux.org/viewtopic.php?id=212819 for that.
  • 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.
  • Why are llvm development versions needed ?
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 Aur llvm-git (2 packages).
There are Alternatives, if you want to use them edit the PKGBUILD.
  • how to update
run pacman Syu
build & update llvm-git & lib32-llvm-git
run pacman -Syu

build mesa-git
log out , restart X .
build lib32-mesa-git

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Terence commented on 2019-06-10 19:06

Thanks Lone_Wolf for pointing me to the right direction. I successfully created my own patch based on the MR, modified the libglvnd PKGBUILD to apply it and the missing files are now provided.

I opened a feature request on the tracker: https://bugs.archlinux.org/task/62869 Feel free to upvote it if you also have this problem and try the attached PKGBUILD and patch.

Lone_Wolf commented on 2019-06-10 10:58

Mesa 19.1 will include that commit, so both mesa-git and stock mesa would have to revert the commit.

Solving this in libglvnd is a much better solution .

The glvnd bug has a proposed patch (from april 28 ), try applying that to the glvnd package using abs/asp . Anyone willing to start a patched glvnd package should/could ask help on forum or arch-general, aur-general mailing lists.

https://github.com/NVIDIA/libglvnd/pull/86

Terence commented on 2019-06-09 02:10

Since https://cgit.freedesktop.org/mesa/mesa/commit/?id=b01524fff05eef66e8cd24f1c5aacefed4209f03, mesa doesn't provide libGLESv2.so and glesv2.pc anymore resulting in building problems: https://bugs.freedesktop.org/show_bug.cgi?id=110141 Can the commit be reverted until libglvnd behaves correctly?

Lone_Wolf commented on 2019-06-04 15:16

Thanks, Faalagorn.

Working on adjusting to that.

Lone_Wolf commented on 2019-06-04 15:15

AUR Helpers are NOT supported

I built and test with makepkg. Building with Devtools and Clean Chroot Manager should work fine also (I test them occasionally).

This package and lib32-mesa-git use a custom method to dynamically determine which llvm version is to be used. Several AUR helpers (atleast pamac and yay) can't handle that method.

Incase you try to build mesa-git with one of those AUR helpers, run makepkg --printsrcinfo > .SRCINFO after downloading and BEFORE building.

That should help pamac and yay to handle my custom method.

Faalagorn commented on 2019-06-02 23:36

lordheavy finally switched from -svn to -git in the "mesa-git" unofficial repo, so the PKGBUILDs might require an update to reflect that :)

Lone_Wolf commented on 2019-05-30 18:39

That sounds like those aur helpers use .SRCINFO to determine needed dependencies instead of the PKGBUILD itself.

The way this PKGBUILD works is that the real makedeps & deps are determined at buildtime.

It seems there's an implicit assumption in SRCINFO : the information in it is static and doesn't change.

For mesa-git and lib32-mesa-git that assumption fails.

I'm going to create a thread in AUR Issues, Discussion & PKGBUILD Requests forum board to discuss this.

yurikoles commented on 2019-05-30 16:49

but AUR helpers, e.g. yay want to install llvm-minimal-git before mesa-git

Lone_Wolf commented on 2019-05-30 13:17

Changed how NINJAFLAGS is used, package should now build ok if it's not defined.

That's correct yurikoles.

makepkg --printsrcinfo does process the PKGBUILD, sees MESA_WHICH_LLVM is set to 1 on my system, writes llvm-minimal-git as makedep and llvm-libs-minimal-git as dep in .SRCINFO .

When the user runs makepkg, it will use their systems value of MESA_WHICH_LLVM . If they haven't set it, makepkg will use the default of 4 and use extra llvm / llvm-libs .

The end result is : action is needed to build mesa-git against any llvm trunk version.

yurikoles commented on 2019-05-30 11:16

@Lone_Wolf, there is llvm-minimal-git in makedepends in .SRCINFO.