[PATCH 2/2] Update .pc file Requires lines to express full dependencies

Keith Packard keithp at keithp.com
Wed Feb 12 20:52:13 PST 2014


Alan Coopersmith <alan.coopersmith at oracle.com> writes:

> Dependencies via libraries should be tracked via linking the libraries so
> the ELF data records them correctly.

Yeah, that's not the problem these changes are trying to solve.

> If the headers are required, the dependencies should appear on the
> Requires.private: line, not the Requires: line - for most X software,
> the Requires line should be nearly empty, and most things expressed
> on Requires.private (which also handles static linking if needed).

As the referenced modules almost always provide part of the relevant API
(especially datatypes), I'm not sure this is correct. These requirements
aren't hidden behind the API, they're part of the API.

My understanding of Requires.private was that it was for hidden
implementation details (like the XML library used to parse fontconfig
configuration files) so that static linking would know to pull in the
dependency.

But, I'm probably just not understanding the subtle difference between
Requires and Requires.private...

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 810 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20140212/96d1d07d/attachment.pgp>


More information about the xorg-devel mailing list