| Summary: |
document specifying direct path to .pc files |
| Product: |
pkg-config
|
Reporter: |
Nathan Phillip Brink (binki) <ohnobinki> |
| Component: |
src | Assignee: |
Tollef Fog Heen <tfheen> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| Hardware: |
Other | |
|
| OS: |
All | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
| Attachments: |
pkg-config-dot-pc-cmdline-syntax.patch
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 41405 [details] pkg-config-dot-pc-cmdline-syntax.patch I sometimes use the form $ pkg-config --libs ./libstrl.pc form of calling pkg-config. This is useful, for example, as a quick check when testing that one's ./configure script or Makefile is producing correctly formatted .pc files. It's also useful when one wants to have greater control over a particular project's build, such as when statically linking against a bundled library which supports pkg-config. However, this syntax is not documented in pkg-config(1) from what I can see. I will have attached a patch which at least mentions this feature, but I would like to see the manpage at least discuss this form of calling pkg-config. Because the current manpage doesn't discuss this form, I don't know if it's an intended feature intended to be kept in future versions. I also don't know if I am required to use absolute paths or if $ pkg-config --libs libstrl.pc is considered valid. Even if the changes in my patch do not agree with the intended use of the discussed feature, I would much appreciate if some similar change were done.