The upstream doesn't supply this file as well. But at least the debian does so. It would be nice that gentoo do the same way. Reproducible: Always
Created attachment 402578 [details] libcrypto++.pc.in file Here is a pc.in file to be used in the ebuild (fairly stolen from debian package).
Created attachment 402580 [details, diff] the propoused patch for the ebuild Here is a propoused patch. also it requres above file to be placed in the FILESDIR.
Note that it's typically frowned upon to make downstream additions/modifications to pkg-config files.
Have you tried to approach upstream to add this?
(In reply to Alon Bar-Lev from comment #4) > Have you tried to approach upstream to add this? Nope, I haven't... As far as upstream haven't incorporated autotools (or some other modern enough build system) and uses general Makefile, I don't know even how to start the talk about a *.pc file. According to mail-archive there were a thread about it on the maillist several years ago, but it seems it result in nothing but patching the debian package with autotools: http://www.mail-archive.com/cryptopp-users%40googlegroups.com/msg04378.html Also I'm not sure how alive the upstream is: there was no commit to svn since last release.
This should be closed as invalid IMO. As already said, this is not packager business.
Fixed.
(In reply to Jason A. Donenfeld from comment #7) > Fixed. Do you want to be a maintainer of this package? If so, please assign your self, remove crypto.
Reverted, poor quality. 1. Not sure why you copy and then sed -i, while you can sed to final destination. 2. Not sure why you use WORKDIR and not T. 3. If the file is a template, it should be with .in suffix and substs should be standard @v@ Regardless, when we add patches we first submit to upstream for acceptance. This means that it should write it in proper way for them to be merged. Once again, having a pkg-config is upstream task, downstream should not add such by its own, it may create a lot of breakages.
Also see [1] for upstream handle. If it is a require artifact, feel free to discuss it here. So far we did not find mandatory reason to include it as many other libraries whose upstream do not provide it. [1] https://github.com/weidai11/cryptopp/issues/133
@Bar-Lev reverting your revert helped to compile the media-sound/clementine-1.3 Whats the point of a dev-lib existing but not usable? As a hobbyista Gentoo user I needed two hours to find out. ... not amused about Gentoo developers fighting.
(In reply to Ulenrich from comment #11) > @Bar-Lev > reverting your revert helped > to compile the media-sound/clementine-1.3 > > Whats the point of a dev-lib existing but not usable? > As a hobbyista Gentoo user I needed two hours to find out. > ... not amused about Gentoo developers fighting. I do not know what is media-sound/clementine-1.3, nor do I know if it can be modified to be built with libcrypto++ upstream without pkg-config.
it cannot been built, see my tries at: https://bugs.gentoo.org/show_bug.cgi?id=580134#c1
Upstream is against pkg-config, dependencies should not require it.
