Displaying 3 results from an estimated 3 matches for "pc_path".
Did you mean:
lc_path
2019 Jul 25
2
bcachefs-tools
...t directory will
always be searched after searching the path; the default is
libdir/pkgconfig:datadir/pkgconfig where libdir is the libdir for
pkg-config and datadir is the datadir for pkg-config when it was
installed.
On my installation, the current path seems to be:
~$ pkg-config --variable pc_path pkg-config
/usr/lib64/pkgconfig:/usr/share/pkgconfig
~$ echo $PKG_CONFIG_PATH
<<produces no output>>
Using locate, I do not find any of these files, so how do I properly
add the packages to the path --
`blkid.pc'
`uuid.pc'
`libsodium.pc'
`libzstd.pc'
Thanks for readin...
2019 Jul 25
0
bcachefs-tools
...searched after searching the path; the default is
> libdir/pkgconfig:datadir/pkgconfig where libdir is the libdir for
> pkg-config and datadir is the datadir for pkg-config when it was
> installed.
>
> On my installation, the current path seems to be:
> ~$ pkg-config --variable pc_path pkg-config
> /usr/lib64/pkgconfig:/usr/share/pkgconfig
>
> ~$ echo $PKG_CONFIG_PATH
> <<produces no output>>
>
> Using locate, I do not find any of these files, so how do I properly
> add the packages to the path --
> `blkid.pc'
> `uuid.pc'
> `lib...
2007 Aug 07
1
pkgconfig fix for nut
Dear Stanislav,
thanks for your patch. The problem with your "recommended"
pkgconfigdir is that in many cases, it does not work. Namely, when
${prefix} is not one of the standard places such as /usr.
As I understand it, the whole point of a tool like pkgconfig is to
allow other software to automatically detect the install location of
NUT, especially when that location is not one of