Package Details: mesa-aco-git 20.1.0_devel.20200417.4b94b901337-8

Git Clone URL: https://aur.archlinux.org/mesa-aco-git.git (read-only, click to copy)
Package Base: mesa-aco-git
Description: Mesa with the ACO compiler patchset, git version
Upstream URL: https://www.mesa3d.org
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-git, mesa-vdpau, mesa-vulkan-layer, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-radeon
Provides: libva-mesa-driver=20.1.0_devel.20200417.4b94b901337-8, mesa=20.1.0_devel.20200417.4b94b901337-8, mesa-git=20.1.0_devel.20200417.4b94b901337-8, mesa-libgl=20.1.0_devel.20200417.4b94b901337-8, mesa-vdpau=20.1.0_devel.20200417.4b94b901337-8, mesa-vulkan-layer=20.1.0_devel.20200417.4b94b901337-8, opencl-driver, opencl-mesa=20.1.0_devel.20200417.4b94b901337-8, opengl-driver, vulkan-driver=20.1.0_devel.20200417.4b94b901337-8, vulkan-intel=20.1.0_devel.20200417.4b94b901337-8, vulkan-mesa-layer=20.1.0_devel.20200417.4b94b901337-8, vulkan-radeon=20.1.0_devel.20200417.4b94b901337-8
Submitter: Nephyrin
Maintainer: Nephyrin
Last Packager: Nephyrin
Votes: 6
Popularity: 0.93
First Submitted: 2019-10-06 18:28
Last Updated: 2020-04-19 21:16

Dependencies (36)

Required by (1000)

Sources (3)

Pinned Comments

Nephyrin commented on 2019-10-06 22:16

If anyone is having a circular issue where they cannot -Syu due to their mesa-aco-git build, you'll need to switch back to regular mesa, do a proper upgrade, and then rebuild mesa-aco-git. The recent libglvnd changes mean this package must be built in the presence of libglvnd>=1.2.0 to prevent issues.

I've bumped the build dep accordingly to hopefully prevent people from getting stuck.

Nephyrin commented on 2019-10-06 18:30

See here for information on the ACO backend: https://steamcommunity.com/games/221410/announcements/detail/1602634609636894200

While some bits of ACO have been merged to upstream mesa, this branch still contains the latest development work, and also enables ACO features by default.

This package is mesa-git targeted at the ACO branch. It selects llvm 8.0 to prevent breaking your system when llvm9 comes out (rebuild will be required). Unlike mesa-git this doesn't have the MESA_WHICH_LLVM selection, which we were seeing break AUR helpers such as yay, but that may be a matter of preference. Using llvm-git is much less necessary with this as the new compiler, by definition, is not using LLVM (some non-pixel-shaders still make use of system LLVM, but 8.0 should be plenty recent for those purposes)

Latest Comments

1 2 3 4 Next › Last »

Nephyrin commented on 2020-04-29 17:05

As commented below, aco is largely in upstream mesa now -- the difference in packages is what they are tracking, moreso than simply turning ACO on by default. This package is aimed at the primary ACO developer's branch, which often has patches before they are upstream, and is rebased periodically on known good commits for ACO usage. It also has aco on by default, rather than opt-in.

Those not wanting to follow bleeding-edge ACO patches can simply use mesa-git with RADV_PERFTEST=aco in their environment. For most gaming usage, there is increasingly little difference.

FooisOP commented on 2020-04-29 16:57

@Strykar,

how do I install the patch? There is no instructions.

ssorgatem commented on 2020-04-24 22:30

I get the following error when installing this package and the lib32 version:

/usr/bin/mesa-overlay-control.py exists in both: "mesa-aco-git" and "lib32-mesa-aco-git".

Strykar commented on 2020-04-22 17:33

For gaming on Linux, you should be using the mesa-git package, as suggested by GloriousEggroll on Discord:

"I use mesa-git with a patch that enables ACO by default
at this point mesa-aco-git is useless as the author forked the work on gitlab and submits prs directly to mesa"
https://gitlab.com/GloriousEggroll/mesa/-/blob/master/radv_aco_enable_ACO_by_default.patch

ababa commented on 2020-04-19 16:16

just a heads up, llvm got updated and PKGBUILD needs to be updated, I think

gardotd426 commented on 2020-02-05 21:23

@Nephyrin, okay that makes much more sense, however it seems like the original comment made about switching has since been removed (I can't find it on here), and the way it was worded specifically made it seem like it was being based against regular Mesa because ACO was in mainstream stable Mesa now. So surely you can understand my concerns. Since that comment was made, I switched to the valveaur binary package, but I always prefer to have it compiled on my system so going by what you're saying now I'll switch back to this.

Nephyrin commented on 2020-02-05 21:09

@gardotd426 This package is pointed at the "actual" dev branch of the ACO developer, with additional ACO development work staged that is not upstream: https://github.com/daniel-schuermann/mesa

It is identical to the lib32-mesa-aco-git package in that regard. The reason it currently says 19.3 on AUR is because that was what the git revision was at last time it was updated -- but -git packages from AUR always build the latest commit, and you will see it build a proper 20.0 revision when you compile it, or when you use the Valve AUR repository.

gardotd426 commented on 2020-02-05 09:46

Again, @Nephyrin, I strongly believe this package should go back to being the actual mesa-aco-git package, instead of regular mesa with RADV_PERFTEST=aco being automatically applied on top of regular stable mesa. For one, that's just a single environment variable that anyone can do with regular mesa in one second, which eliminates this package's need for existing in the first place, but more importantly, you're now only getting 19.3.2 as opposed to the 20.0.0_devel/20.0.0-rc of mesa-git or the actual mesa-aco-git branch from valve themselves, so this is also quite behind in development compared to where it was before it was changed. Not only that, lib32-mesa-aco-git is still the proper one, and so it's still on 20.0.0_devel, and I feel like that also makes little sense having the 64-bit and 32-bit versions be on different releases. Also as I said before, it's a fact that mesa-git and valve's mesa-aco branch have things not implemented upstream into vanilla non-development-branch mesa. And this being a package called mesa-aco-git, people are going to be rightfully expecting to be getting actual mesa-aco-git, not regular mesa with an environment variable activated.

So, basically, the only actual reason for this package to be changed to its current state and not the way it's supposed to be, the way it was, or the name implies seems to be to make it maybe slightly easier to maintain or something? Either way, it makes no sense.

regulator commented on 2020-02-05 03:12

Enkhiel, there is no manjaro support on here, I will send you a message

Enkhiel commented on 2020-02-04 22:08

Was trying to Build this as well using pamac in Manjaro but jsut get a bunch of errors that dependencies (mostly related to mesa) cannot be resolved:

das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von gst-plugins-base-libs das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von gtk3 das Entfernen von lib32-mesa verletzt Abhängigkeit von 'lib32-mesa' benötigt von lib32-gtk3 das Entfernen von lib32-mesa verletzt Abhängigkeit von 'lib32-mesa' benötigt von lib32-libglvnd das Entfernen von lib32-mesa verletzt Abhängigkeit von 'lib32-opengl-driver' benötigt von lib32-libglvnd das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von libglvnd das Entfernen von mesa verletzt Abhängigkeit von 'opengl-driver' benötigt von libglvnd das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von mhwd das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von qt5-base das Entfernen von lib32-mesa verletzt Abhängigkeit von 'lib32-mesa' benötigt von steam-manjaro das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von xf86-video-amdgpu das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von xf86-video-ati das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von xf86-video-intel das Entfernen von mesa verletzt Abhängigkeit von 'mesa' benötigt von xf86-video-nouveau