update README wrt fd.o pkg-config commit c53385b5

feature/tap-sh
William Pitcock 2016-12-24 23:07:59 -06:00
parent 6ef4a853b5
commit fd8927f032
1 changed files with 13 additions and 5 deletions

View File

@ -28,13 +28,21 @@ can run:
## comparison of `pkgconf` and `pkg-config` dependency resolvers ## comparison of `pkgconf` and `pkg-config` dependency resolvers
pkgconf builds an acyclic directed dependency graph. This allows for the user pkgconf builds an acyclic directed dependency graph. This allows for the user
to more conservatively link their binaries -- which may be helpful in some to more conservatively link their binaries -- which may be helpful in some
environments, such as when prelink(1) is being used. As a result of building environments, such as when prelink(1) is being used. As a result of building
a directed dependency graph designed for the specific problem domain provided a directed dependency graph designed for the specific problem domain provided
by the user, more accurate dependencies can be determined. pkg-config, on the by the user, more accurate dependencies can be determined.
other hand builds a database of all known pkg-config files on the system before
attempting to resolve dependencies, which is a considerably slower and less Current release versions of pkg-config, on the other hand, build a database of all
efficient design. known pkg-config files on the system before attempting to resolve dependencies, which
is a considerably slower and less efficient design. Efforts have been made recently
to improve this behaviour.
As of the 1.1 series, pkgconf also fully implements support for `Provides` rules,
while pkg-config does not. pkg-config only provides the `--print-provides` functionality
as a stub. There are other intentional implementation differences in pkgconf's dependency
resolver verses pkg-config's dependency resolver in terms of completeness and correctness,
such as, for example, how `Conflicts` rules are processed.
## linker flags optimization ## linker flags optimization