Package Details: vulkan-intel-git 20.3.0_devel-1

Git Clone URL: https://aur.archlinux.org/vulkan-intel-git.git (read-only, click to copy)
Package Base: vulkan-intel-git
Description: Intel's Vulkan mesa driver
Upstream URL: http://www.mesa3d.org
Licenses: custom
Conflicts: vulkan-i965, vulkan-i965-git, vulkan-intel
Provides: vulkan-intel
Submitter: haagch
Maintainer: haagch
Last Packager: haagch
Votes: 5
Popularity: 0.000000
First Submitted: 2016-02-21 23:13
Last Updated: 2020-09-13 20:47

Latest Comments

« First ‹ Previous 1 2 3

1ace commented on 2016-02-18 23:03

Per spec [1], packages should install manifest files (*.json) in /usr/share/vulkan/icd.d
/etc/vulkan/icd.d is for manually copied files

[1] https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/blob/sdk-1.0.3/loader/LoaderAndLayerInterface.md#properly-installed-icds-1

Edit: now that I think about it, maybe you did this to leave the proper location open for when vulkan gets merged into mainline mesa?
I guess you can just ignore me anyway, since this location works too :]

Edit bis:
I just finished compiling it, and I noticed you have way too many files in this package. The only 3 file that make sense are /etc/vulkan/icd.d/intel_icd.json, /opt/mesa-vulkan/lib/libvulkan_intel.so (which should go either in the same location as the .json, or in /usr/lib/) and /opt/mesa-vulkan/include/vulkan/vulkan_intel.h (which should go in /usr/include/vulkan/)
Everything else is just redundant and will never be used in these location.

You should also depend on `vulkan-icd-loader` (my package in the AUR (`vulkan-loader`) is not going to stay there once the couple bugs in the one in [extra] are fixed) and optdepend on `vulkan-headers` :)

haagch commented on 2016-02-18 22:44

Hm... Yea, I'll wait and see what "basename" to provide they decide on.

neuromancer85 commented on 2016-02-18 22:17

Could you change the dependency on vulkan-loader to vulkan-icd-loader from [extra]?

IncredibleLaser commented on 2016-02-18 18:36

You're correct, python2-mako is a makedepends and so are python and git. Sounds silly since you need git anyways to use the AUR but if you build in a clean chroot it will throw you an error when trying to build.

Xabre commented on 2016-02-18 16:47

checking if module mako in python is installed... No module named mako
no
configure: error: Python mako module v0.3.4 or higher not found

Should depend on python-mako (probably just a makedep)

Em, it's python2-mako, actually.