Package Details: opencl-rusticl-mesa-minimal-git 24.3.0_devel.194673.5db135f66ad-2

Git Clone URL: https://aur.archlinux.org/mesa-minimal-git.git (read-only, click to copy)
Package Base: mesa-minimal-git
Description: OpenCL support in rust for mesa drivers (git version)
Upstream URL: https://www.mesa3d.org
Licenses: MIT AND BSD-3-Clause AND SGI-B-2.0
Conflicts: opencl-clover-mesa, opencl-rusticl-mesa
Provides: opencl-driver, opencl-rusticl-mesa
Submitter: shoober420
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 11
Popularity: 0.010175
First Submitted: 2020-12-10 00:38 (UTC)
Last Updated: 2024-09-11 18:17 (UTC)

Dependencies (47)

Required by (40)

Sources (1)

Pinned Comments

Lone_Wolf commented on 2023-05-22 12:07 (UTC) (edited on 2024-09-06 21:16 (UTC) by Lone_Wolf)

Build order

llvm-minimal-git
spirv-headers-git
spirv-llvm-translator-minimal-git
libclc-minimal-git
mesa-minimal-git

N.B. these packages are closely tied together, make sure you build all of them in a short period of time (worst case on my system is around 3 hours) .

Build frequency

I aim to build everything (including the lib32 part) atleast once a week.

How often you build this is a personal choice, but once a month is in my opinion the absolute minimum .

In that timeframe mesa will have seen almost 1k commits, llvm/clang gets more.

Lone_Wolf commented on 2021-01-22 18:36 (UTC) (edited on 2021-01-22 18:39 (UTC) by Lone_Wolf)

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

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

« First ‹ Previous 1 .. 3 4 5 6 7 8

Lone_Wolf commented on 2021-01-09 14:51 (UTC)

Thanks, I adopted both.

shoober420 commented on 2021-01-09 08:11 (UTC)

I disowned both packages.

Lone_Wolf commented on 2021-01-06 22:55 (UTC) (edited on 2021-01-07 10:18 (UTC) by Lone_Wolf)

Shoober420, please transfer maintainership of this and lib32-mesa-minimal-git to me.

I have a PKGBUILD ready that does differ a lot from mesa-git, builds faster and creates a smaller package.

See https://bbs.archlinux.org/viewtopic.php?id=261629 for details

codewiz commented on 2020-12-12 08:02 (UTC)

Oh, I see. A few minor features and debug options have been turned off. Plus, this version is built with -O3.

Is there any measurable advantage in benchmarks?

codewiz commented on 2020-12-12 07:58 (UTC)

What's the difference between this package and mesa-git? The package description is identical.

« First ‹ Previous 1 .. 3 4 5 6 7 8