Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#75022 - [vulkan-icd-loader] should not be mixed with the devel package
Attached to Project:
Arch Linux
Opened by Nervt Nicht (EinloggenNervt) - Friday, 10 June 2022, 12:38 GMT
Last edited by Toolybird (Toolybird) - Sunday, 31 July 2022, 04:20 GMT
Opened by Nervt Nicht (EinloggenNervt) - Friday, 10 June 2022, 12:38 GMT
Last edited by Toolybird (Toolybird) - Sunday, 31 July 2022, 04:20 GMT
|
DetailsDescription:
The vulkan-icd-loader package is broken, it ships vulkan-dev and the vulkan runtime in one package without adding vulkan-headers as a "must have" depedency This breaks the principle of pkg-config in cmake detection, since you can install the icd loader(which also acts as dev package(library wise)) without needing vulkan-headers. This is not the case on debian: https://packages.debian.org/de/sid/amd64/libvulkan-dev/filelist https://packages.debian.org/de/sid/amd64/libvulkan1/filelist Which makes more sense. Would be nice if you add an additional vulkan-devel package that has a required dependency for vulkan-headers and only adds pkg-config there Additional info: * package version(s): all * config and/or log files etc.: none * link to upstream bug report, if any: none Steps to reproduce: Use pkg-config with cmake (custom find_package), or just think about it. |
This task depends upon
So again the workflow:
- You install a development package for vulkan
- You add a cmake package to find this development package over pkg-config. If they are not found -> cmake error
=> As a developer you except to get all required libraries and includes independent of the distrobution.
Debian did this correct, arch not (IMO). So I have to apply an arch only exception and I think debian has the more convincing solution here, or what exactly are your arguments against it?
Edit:
See the package content on arch:
Package Contents
usr/
usr/lib/
usr/lib/libvulkan.so
usr/lib/libvulkan.so.1
usr/lib/libvulkan.so.1.3.221
usr/lib/pkgconfig/
usr/lib/pkgconfig/vulkan.pc
usr/share/
usr/share/licenses/
usr/share/licenses/vulkan-icd-loader/
usr/share/licenses/vulkan-icd-loader/LICENSE.txt
it ships the package config in this NON development package that has no header requirements.
Edit2:
"pkg-config is a computer program that defines and supports a unified interface for querying installed libraries for the purpose of compiling software that depends on them."
https://en.wikipedia.org/wiki/Pkg-config
I hope this is clear and the issue gets high prio again, bcs it's a "major" bug