<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I don't see that information in the man page (also, I am not familiar enough with pkg-config to know how results described in that man page translate to other systems).<div class=""><br class=""></div><div class="">Specifically, that man page does not seem to document where on disk the .pc files live. How are we going to know that?</div><div class=""><br class=""></div><div class="">For example, one on random VM I have lying about I see .pc files here:</div><div class="">--</div><div class=""><div class="" style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span class="" style="font-variant-ligatures: no-common-ligatures;">/# find / -name \*.pc | xargs dirname | sort | uniq</span></div><div class="" style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span class="" style="font-variant-ligatures: no-common-ligatures;">/usr/lib/pkgconfig</span></div><div class="" style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span class="" style="font-variant-ligatures: no-common-ligatures;">/usr/lib/x86_64-linux-gnu/pkgconfig</span></div><div class="" style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span class="" style="font-variant-ligatures: no-common-ligatures;">/usr/lib/x86_64-linux-gnu/pkgconfig/mit-krb5</span></div><div class="" style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span class="" style="font-variant-ligatures: no-common-ligatures;">/usr/share/pkgconfig</span></div></div><div class="">--</div><div class="">and the pkg-config tool appears to be able to find results from all of those. How would we know those directory names if we don't have a dependency on the actual tool?</div></div></div></blockquote><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">There is a config file and an environment variable.</div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Do you need me to document them completely so that we can move forward with this?</div></div></blockquote></div><br class=""><div class="">No, not at all, I think the proposal makes complete sense and should be moved along.</div><div class=""><br class=""></div><div class="">Nevertheless, I still want to understand how it will work... I might be missing some information from the man page but I just don't see where this is described. It *looks* to me like the default search list is hard coded into the tool.</div></div></div></blockquote><br class=""></div><div>Best docs I have found are: <a href="https://people.freedesktop.org/~dbn/pkg-config-guide.html" class="">https://people.freedesktop.org/~dbn/pkg-config-guide.html</a></div><div><br class=""></div><div>Essentially:</div><div><br class=""></div><div>The std path is /usr/lib/pkg-config and /usr/share/pkg-config, this can be supplemented by an env var PKG_CONFIG_PATH</div><div><br class=""></div><div>It is common for system packagers to add more paths. Eg. brew does this, I coded it myself.</div><div><br class=""></div><div>This is fine, because the additional paths can only be queried by a custom configured pkg-config, and in such cases we can just ask the custom configured pkg-config, if it’s there, there may be more paths, if it’s not then there cannot.</div><br class=""></body></html>