Confirmed, and you only need to add python-packaging .
@Reza : Due to changes in python 3.12 python-packaging is now a required makedepend . This package and it's lib32 counterpart both need it.
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-clover-mesa, 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: | rjahanbakhshi |
Votes: | 178 |
Popularity: | 2.15 |
First Submitted: | 2014-06-19 21:33 (UTC) |
Last Updated: | 2024-04-17 22:44 (UTC) |
Confirmed, and you only need to add python-packaging .
@Reza : Due to changes in python 3.12 python-packaging is now a required makedepend . This package and it's lib32 counterpart both need it.
Was getting a build error about python-mako version or something. Added python-setuptools to the deps list and it builds in a chroot.
@kolaris :
it is possible to build this without llvm, but a lot of drivers will fail that way.
The only x86_64 ones I know of that will work without llvm are radv (vulkan-amd) and zink .
Since zink requires a working vulkan driver, that means only systems with a amd videocard can use this setup.
Is it possible to build this without using llvm? would that be a problem to do so? as in would it negatively impact performance or the other way around, etc...
Yeah, honestly I know this is supposed to be the "catch all" mesa package but honestly who in the heck is using Arch Linux WSL anyway? I don't think the D3D12 needs to be there, I think it can be its own package
I doubt very much the gallium-d3d12 driver is used by vkd3d / vkd3d proton as they translate d3d to vulkan, not to some layer from MS.
vkd3d-proton support is nothing but niche... Edit: Yeah i just tested RE4 without the gallium-d3d12 driver and it seemed to run fine with vkd3d
Since d3d12 gallium driver is only really necessary on a very niche use case, could it be removed from the PKGBUILD?
@ArchUsr1
<h2>Overview</h2>The D3D12 driver is a Gallium driver that emits API calls for Microsoft's :abbr:
D3D12 (Direct3D 12)
API instead of targeting a specific GPU architecture. This can be used to get full desktop OpenGL 3.3 support on devices that only support D3D12.
It's mainly use on WSL(Windows subsystem for Linux).
Not building it won't effect Linux PC.
@charly2k24 I had to delete d3d12
and I'm using directx-headers-git. I'd like to know what's the proper fix for this because I'm not sure if it's used in some games.
Pinned Comments
Lone_Wolf commented on 2024-04-03 16:59 (UTC)
To those with the directx errors : archlinux directx-headers pacakgae is 2 releases behind upstream. Try building against aur directx-headers-git .
I don't remember what d3d12 does, but offical mesa also supports it.
@ZephyrCheez : thanks, that option lead to meson subprojects and mesa sourcetree does appear to include the data needed to use them. Adding nouveau vulkan looks doable now, no idea when there will be time to implement it.
Lone_Wolf commented on 2024-02-20 00:09 (UTC) (edited on 2024-02-20 00:11 (UTC) by Lone_Wolf)
@Beiruty, those have the same cause as the other recent build failures : changes in intel drivers.
The build issues caused by changes in intel drivers are now solved for MESA_WHICH_LLVM 1, 3 and 4 (llvm-minimal-git , llvm from lordheavy unofficial repo and offical repo llvm )
MESA_WHICH_LLVM 2 (aur llvm-git) build is still broken, but I MAY have a solution for that without having to create new packages.
The good news is that once all 4 variants built again, only minor changes should be needed to add opencl clover & opencl rusticl support.
(A lot of the work required to built the intel drivers is also useful for clover & rusticl)
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.
Option A - best one
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.
Option B - 2nd best
Lone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)
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 ?
Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)
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 functionalitybuild lib32-mesa-git
run
glxinfo32 -B
to verify basic OpenGL functionality for multilib programs