Package Details: vulkan-caps-viewer 2.2-1

Git Clone URL: (read-only, click to copy)
Package Base: vulkan-caps-viewer
Description: Vulkan Hardware Capability Viewer
Upstream URL:
Keywords: gpu vulkan
Licenses: GPL2
Submitter: 1ace
Maintainer: 1ace
Last Packager: 1ace
Votes: 43
Popularity: 0.41
First Submitted: 2016-02-21 21:17
Last Updated: 2020-08-01 20:46

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

1ace commented on 2019-11-29 11:55


Well, what about vulkan-headers-git then?

there's no way to know if the user's build of that package would be recent enough, making it entirely unusable for this situation.

If the package requires qt5-base then there's no need for it to be in makedepends.

what is needed for building and for running are two independent sets, you can't ignore things in one because they're in the other

Building needs to be in the build() array, not in prepare().

this package is not building anything in prepare(), I'm not sure what you mean?

Here's an improved PKGBUILD [...]

most of your changes are not actually doing anything, but I did move the git clone/fetching to makepkg, which will avoid the full clone when doing a clean build from an already-used PKGBUILD :)

yochananmarqos commented on 2019-10-08 23:50

Well, what about vulkan-headers-git then?

If the package requires qt5-base then there's no need for it to be in makedepends.

Building needs to be in the build() array, not in prepare().

1ace commented on 2019-10-08 23:08

No, the point is precisely to use the latest headers, regardless of what is currently shipped in the arch package.

yochananmarqos commented on 2019-10-08 22:52

Can the vulkan-headers package be used instead of the submodule? Isn't there a qmake flag to force it to use system libs?

1ace commented on 2019-10-08 19:09

I'm aware, I've already update the vulkan-caps-viewer-bin package, but there's an issue upstream with the tarball that prevents it from building.

I'm talking to the upstream maintainer to find a solution, and may have to hack it in the package to make it build, but I'll wait for now as I would prefer a clean upstream solution.

yochananmarqos commented on 2019-10-08 18:42

For some reason I can't flag anything out of date today. v2.02 is out:

EDIT: It turns out it is being marked out of date, but it doesn't show it here.

ssorgatem commented on 2018-10-02 10:18

It's failing to build for me:

' In file included from vulkanDeviceInfo.hpp:42, from vulkancapsviewer.h:14, vulkanresources.h:355:14: error: explicit specialization in non-namespace scope ‘class vulkanResources’ ^ vulkanresources.h:361:14: error: explicit specialization in non-namespace scope ‘class vulkanResources’ template<> ^ In file included from vulkancapsviewer.h:14, from main.cpp:1: GeneratedFiles/release/../../vulkanresources.h:355:14: error: explicit specialization in non-namespace scope ‘class vulkanResources’ template<> ^ template<> In file included from GeneratedFiles/release/../../vulkancapsviewer.h:14, GeneratedFiles/release/../../vulkanDeviceInfo.hpp: In member function ‘QJsonObject VulkanDeviceInfo::toJson(std::cxx11::string, std::cxx11::string, std::__cxx11::string)’: template<> ^ QJsonObject toJson(std::string fileName, std::string submitter, std::string comment) In file included from vulkancapsviewer.cpp:41: vulkancapsviewer.cpp: In member function ‘void vulkanCapsViewer::displayDevice(int)’: vulkancapsviewer.cpp:710:15: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<vulkandeviceinfo>::size_type’ {aka ‘long unsigned int’} [-make: *** [Makefile:1040: release/vulkancapsviewer.o] Error 1 '</vulkandeviceinfo>

HeroCC commented on 2018-08-30 02:25

@ecloud try the fix here:

ecloud commented on 2017-10-25 08:15

"Could not enumarted device count!" [sic]

It's a typo, bad grammar _and_ unexpected behavior all in one.

lspci says

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]

It works fine for X11, wayland and OpenGL.

OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2

But other Vulkan programs give VK_ERROR_INITIALIZATION_FAILED.

1ace commented on 2017-05-29 13:40

Just realized I forgot to reply to everyone lately:

krant: added (6 months ago ^^), thanks!

pums974: this error came from the server, not the client. I expect it's been solved a long time ago though.

hcorion: renaming packages is a pain (getting users to move to the new package), so I won't be doing this, but I'll try and think about it next time :)
lubosz has made a -git version of this package that compiles from source (with a couple needed changes to the sources to make it compile), which I was planing on doing at some point but didn't have the time (and kinda forgot). Thanks lubosz!

dkadioglu: just pushed your change, and I should've known it was needed. Like I said though, I don't use anything that shows these icons, so I couldn't see for myself it was broken.