Package Details: mesa-minimal-git 21.2.0_devel.138224.f601fd635bb-1

Git Clone URL: https://aur.archlinux.org/mesa-minimal-git.git (read-only, click to copy)
Package Base: mesa-minimal-git
Description: an open-source implementation of the OpenGL specification, stripped down git version
Upstream URL: https://www.mesa3d.org
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Provides: libva-mesa-driver, mesa, opencl-driver, opencl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layer, vulkan-radeon, vulkan-swrast
Submitter: shoober420
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 5
Popularity: 0.25
First Submitted: 2020-12-10 00:38
Last Updated: 2021-04-15 14:02

Required by (1000)

Sources (2)

Pinned Comments

Lone_Wolf commented on 2021-01-22 18:36

Why does this package hard depend on llvm-minimal-git ?

  • performance

archlinux repo packages are build with -march=x86-64 -mtune=generic which works on lots of machines but makes limited use of modern processor capabilities. For many packages this has little impact, but with llvm my experience is different.

My local builds for llvm / mesa are done with -march=native and this has a noticeable effect on their performance.

How big the benefit of this is depends heavily on the exact hardware you use. Worse, the software setup also impacts this. The only way to find out if it benefits your system/software setup is to try it out yourself.

  • easier maintenance and troubleshooting

Since i started my first mesa trunk package late in 2010 I have maintained versions without any llvm, one llvm implementation, split versions, singular versions, versions supporting multiple llvm implementations , switch from libgl hacks libglvnd to allow mesa & nvidia to cooperate etc.

Depending on one llvm variant in a non-splitted singular version results in a simple PKGBUILD that is easy to maintain.

Troubleshooting is also much easier if maintainer uses the same llvm variant as users.

If people feel those reasons are not good enough to hard depend on llvm-minimal-git , maybe I should transfer ownership .

Lone_Wolf commented on 2021-01-09 15:02

Why does this exist ?

Basically mesa/mesa-git build almost everything they can build.

This package tries to build just enough so everyone can use it, but disables older and/or unused components.

Check https://bbs.archlinux.org/viewtopic.php?id=261629 for a discussion about this package.

Latest Comments

1 2 Next › Last »

xenu commented on 2021-03-03 08:38

The recently added patch '0002-fix-ac_build_atomic_rmw-with-LLVM-13.patch' can be removed again as it was merged upstream (and results in an error during prepare).

phush0 commented on 2021-02-22 13:52

Thank you for instructions, I have added same patch found in llvm bug tracker (proposed by you), to allow me to build.

Lone_Wolf commented on 2021-02-22 13:32

I've added a patch that does allow building opencl again.

Incase you still want to disable opencl , replace icd with disabled in the line -D gallium-opencl=icd \

phush0 commented on 2021-02-22 09:50

how to disable opencl building ?

Lone_Wolf commented on 2021-01-30 22:28

Building with opencl enabled gives a new build failure , see https://gitlab.freedesktop.org/mesa/mesa/-/issues/4200

tb0n3 commented on 2021-01-22 19:03

This is perfectly acceptable to me. I just wasn't aware of the change as it had worked previously and then builds suddenly required a change in dependencies. My only reason previously for maintaining llvm versus llvm-minimal-git was the complex dependency workarounds with MESA_WHICH_LLVM which didn't play well with yay, or makepkg for that matter.

Thank you for the explanation and for your work in maintaining these packages.

Lone_Wolf commented on 2021-01-22 18:36

Why does this package hard depend on llvm-minimal-git ?

  • performance

archlinux repo packages are build with -march=x86-64 -mtune=generic which works on lots of machines but makes limited use of modern processor capabilities. For many packages this has little impact, but with llvm my experience is different.

My local builds for llvm / mesa are done with -march=native and this has a noticeable effect on their performance.

How big the benefit of this is depends heavily on the exact hardware you use. Worse, the software setup also impacts this. The only way to find out if it benefits your system/software setup is to try it out yourself.

  • easier maintenance and troubleshooting

Since i started my first mesa trunk package late in 2010 I have maintained versions without any llvm, one llvm implementation, split versions, singular versions, versions supporting multiple llvm implementations , switch from libgl hacks libglvnd to allow mesa & nvidia to cooperate etc.

Depending on one llvm variant in a non-splitted singular version results in a simple PKGBUILD that is easy to maintain.

Troubleshooting is also much easier if maintainer uses the same llvm variant as users.

If people feel those reasons are not good enough to hard depend on llvm-minimal-git , maybe I should transfer ownership .

tb0n3 commented on 2021-01-21 15:39

Is there a reason you now require llvm-minimal-git when regular llvm from the standard repos builds fine? I'd be fine if there was a bug or build reason, but I haven't seen evidence of breakage.

Lone_Wolf commented on 2021-01-09 15:02

Why does this exist ?

Basically mesa/mesa-git build almost everything they can build.

This package tries to build just enough so everyone can use it, but disables older and/or unused components.

Check https://bbs.archlinux.org/viewtopic.php?id=261629 for a discussion about this package.

Lone_Wolf commented on 2021-01-09 14:51

Thanks, I adopted both.