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 (1301)

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 .. 51 52 53 54 55 56 57 58 59 60 61 .. 131 Next › Last »

Lone_Wolf commented on 2019-05-26 14:07 (UTC)

I'd prefer issues with diff files attached over pull requests or merge requests , but neither is currently possible within AUR.

CI sounds nice especially with 4 choices for dependencies, but those docker images would have to be updated atleast several times a week. Maybe if llvm-git & llvm-minimal-git were also included the extra work is worth it.

That suggests this shouldn't be a one-person initiative. How flexible are gitlab / github for setting up and managing a small collaboration ?

Gitlab seems to be a bit friendlier towards open source then github and gitlab source code is available. If all other things are equal, I'd prefer gitlab I think.

One question we should answer before doing anything is : What license will files be published under ? In my opinion PKGBUILD and related files are not original works, so don't have any copyright attached. No idea how to express that in a icense though.

yurikoles commented on 2019-05-25 06:59 (UTC)

Or even GitLab, which offers free CI, so we can test pull requests in Arch Linux Docker.

yurikoles commented on 2019-05-25 06:57 (UTC)

Could you please mirror your AUR packages to GitHub to review pull requests?

yurikoles commented on 2019-05-23 11:56 (UTC)

Sorry, my bad, I had forgotten that this package is being built by meson. Could you please add it to llvm then?

The .gitignore file is for AUR repo, not for mesa one. The other minor changes is about removing unnecessary white spaces.

Lone_Wolf commented on 2019-05-23 11:51 (UTC)

I re-checked and ninja does choke when the environment var is an empty string.

Since that's a valid value for environment variables I have to protect against it.

Lone_Wolf commented on 2019-05-23 11:04 (UTC) (edited on 2019-05-23 11:09 (UTC) by Lone_Wolf)

Thanks for alerting me the patch is no longer needed, Snoop05 .

@Yurikoles :

I've had issues when setting NINJAFLAGS="" aka an empty string. That's a valid value for an environment variable but ninja did seem to choke on it, have to re-test though.

About the patch :

Why should CMAKE flags be send to meson ? Maybe those flags should be added in the llvm/clang packages that do use cmake ?

The local gitrepo folders I use are an exact copy of their upstream counterparts, building is done elsewhere. I don't need gitignore files, why should they be added and stored in the aur git repo ?

yurikoles commented on 2019-05-23 08:06 (UTC)

@Lone_Wolf it seems that check for ninja flag env var is unnecessary, it's safe to pass it unconditionally, if it's empty ninja will just run without flags.

yurikoles commented on 2019-05-22 17:10 (UTC) (edited on 2019-05-22 17:12 (UTC) by yurikoles)

@Lone_Wolf please propagate CMAKE_C_FLAGS and CMAKE_CXX_FLAGS from CFLAGS https://cmake.org/cmake/help/v3.12/variable/CMAKE_LANG_FLAGS.html

Here is patch: also fixed some formatting and added .gitignore:

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..506d336
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,4 @@
+mesa
+pkg
+src
+*.pkg.*
\ No newline at end of file
diff --git a/PKGBUILD b/PKGBUILD
index 6bb2337..dea4ba9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -41,7 +41,7 @@ sha512sums=('SKIP'
 # 2: llvm-git (aur)
 # 3  llvm-svn (lordheavy unofficial repo)
 # 4  llvm (stable from extra) Default value
-# 
+#
 if [[ ! $MESA_WHICH_LLVM ]] ; then
     MESA_WHICH_LLVM=4
 fi
@@ -69,11 +69,7 @@ case $MESA_WHICH_LLVM in
         ;;
     *)
 esac
-        
-        
-        
-        
-        
+
 pkgver() {
     cd mesa
     read -r _ver <VERSION
@@ -83,11 +79,10 @@ pkgver() {
 prepare() {
     # although removing _build folder in build() function feels more natural,
     # that interferes with the spirit of makepkg --noextract
-    if [  -d _build ]; then
+    if [ -d _build ]; then
         rm -rf _build
     fi
     cd mesa
-    patch -Np1 -i "$srcdir"/0001-radeonsi-fix-a-regression-in-si_rebind_buffer.patch
 }

 build () {
@@ -123,19 +118,19 @@ build () {
        -D gallium-opencl=icd \
        -D valgrind=false \
        -D vulkan-overlay-layer=true \
-       -D tools=[]
-       
+       -D tools=[] \
+       -D CMAKE_C_FLAGS="${CFLAGS}" \
+       -D CMAKE_CXX_FLAGS="${CXXFLAGS}"
+
     meson configure _build
     if [[ ! $NINJAFLAGS ]]; then
-        ninja  -C _build 
+        ninja -C _build
     else
-        ninja  "$NINJAFLAGS" -C _build
+        ninja "$NINJAFLAGS" -C _build
     fi
 }

-
 package() {
-
   DESTDIR="$pkgdir" ninja -C _build install

   # indirect rendering

Snoop05 commented on 2019-05-22 15:53 (UTC) (edited on 2019-05-22 15:54 (UTC) by Snoop05)

0001-radeonsi-fix-a-regression-in-si_rebind_buffer.patch is no longer neccessary (merged)

Lone_Wolf commented on 2019-05-20 14:28 (UTC)

commit https://cgit.freedesktop.org/mesa/mesa/commit/?id=78e35df52aa2f7d770f929a0866a0faa89c261a9 causes visual corruption and GPU faults on several types of AMD cards.

That specific commit is reverted in prepare() now.

See https://bugs.freedesktop.org/show_bug.cgi?id=110701 https://bugs.freedesktop.org/show_bug.cgi?id=108824

« First ‹ Previous 1 .. 51 52 53 54 55 56 57 58 59 60 61 .. 131 Next › Last »