On Wed, 2020-04-29 at 12:03 +0100, Bruce Richardson wrote: > On Wed, Apr 29, 2020 at 11:40:33AM +0100, Luca Boccassi wrote: > > On Wed, 2020-04-29 at 11:08 +0100, Bruce Richardson wrote: > > > When calling pkg-config --static --libs, pkg-config will always output the > > > regular libs first, and then the extra libs from libraries.private field, > > > since the assumption is that those are additional dependencies for > > > building > > > statically that the .a files depend upon. > > > > > > However, for DPDK, we only link the driver files for static builds, and > > > those need to come *before* the regular libraries. To get this result, we > > > need two pkgconfig files for DPDK, one for the shared libs, and a second > > > for the static libs and drivers, which depends upon the first. Using a > > > dependency means that the shared libs are printed only after the > > > libraries.private field rather than before. > > > > A neat trick! Can we document that the new file is an implementation > > detail for internal usage, and that it should not be referenced > > directly? > > I'm even pondering if it would be possible to install it in a private > > directory, need to check if there's a way for Requires to specify > > prefixes > > > That would be great, if there was a way to hide it. I also take it from > your feedback that a package needing multiple .pc files is not an issue for > debian packaging?
Yeah it's fine, we can ship as many as we want - just concerned about it being used by mistake, but documenting it should be enough -- Kind regards, Luca Boccassi
