Created attachment 1666930 [details] pkgconfig for zita-convolver Description of problem: Package zita-convolver-devel contains the include file and library to use zita-convolver in applications. However, it does not contain the associated pkgconfig file. Version-Release number of selected component (if applicable): 4.0.3 How reproducible: Always. Steps to Reproduce: 1. pkg-config zita-convolver --libs Actual results: Package zita-convolver was not found in the pkg-config search path. Expected results: -lzita-convolver Additional info: The attached pkgconfig file seems to work most of the times but I'm not a pkgconfig wizard...
zita-convolver never shipped a pkgconfig file, upstream tarball does not contain it. I will ask if out policy permits the creation of a pkgconfig file and if permitted I will add one; the one you attached seems ok.
The attached .pc file contains hardcoded values, on the other hand. The upstream project can't ship the file without further modifications. And since the upstream source tarball doesn't use Autotools but only includes a hardcoded Makefile, more work will be needed to generate a valid .pc file and fill in values based on build-time variables. Generally, the benefit of .pc files only starts when depending projects start using pkg-config to check for library existance, version, cflags, ldflags and possibly other variables. For very simple libs with trivial cflags/ldflags, the benefit is very small, almost negligible.
Yes... Main problem is that certain projects use pkg-config to check for the existence of libraries. And if that is buried deep down customized config scripts it is hard to repair. I can find my way around it, but others may run into the same problems.
Created attachment 1667157 [details] Suggested enhancement for the spec file Is this more useful?
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.