why are .pc files not listed in one place
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am on Debian buster. I was reading the manpage of pkg-config and found that .pc files are and can be listed in many places . From the manpage -
pkg-config retrieves information about packages from special
metadata files. These files are named after the package, and has a .pc
extension. On most systems, pkg-config looks in /usr/lib/pkgconfig,
/usr/share/pkgconfig, /usr/local/lib/pkgconfig and
/usr/local/share/pkgconfig for these files. It will additionally look
in the colon-separated (on Windows, semicolon-separated) list of
directories specified by the PKG_CONFIG_PATH environment variable.
- From pkg-config manpage
sure enough I saw that there are packages in /usr/lib/pkgconfig/, /usr/lib/x86_64-linux-gnu/pkgconfig/ and /usr/share/pkgconfig/ , while I can understand the /usr/local/.. part for locally compiled/built apps. I do not understand why there is a distinction between /usr/lib/pkgconfig/ and /usr/share/pkgconfig . Is it something to do with some things need to be in userspace https://en.wikipedia.org/wiki/User_space or something else entirely ?
debian libraries pkg-config
add a comment |Â
up vote
0
down vote
favorite
I am on Debian buster. I was reading the manpage of pkg-config and found that .pc files are and can be listed in many places . From the manpage -
pkg-config retrieves information about packages from special
metadata files. These files are named after the package, and has a .pc
extension. On most systems, pkg-config looks in /usr/lib/pkgconfig,
/usr/share/pkgconfig, /usr/local/lib/pkgconfig and
/usr/local/share/pkgconfig for these files. It will additionally look
in the colon-separated (on Windows, semicolon-separated) list of
directories specified by the PKG_CONFIG_PATH environment variable.
- From pkg-config manpage
sure enough I saw that there are packages in /usr/lib/pkgconfig/, /usr/lib/x86_64-linux-gnu/pkgconfig/ and /usr/share/pkgconfig/ , while I can understand the /usr/local/.. part for locally compiled/built apps. I do not understand why there is a distinction between /usr/lib/pkgconfig/ and /usr/share/pkgconfig . Is it something to do with some things need to be in userspace https://en.wikipedia.org/wiki/User_space or something else entirely ?
debian libraries pkg-config
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am on Debian buster. I was reading the manpage of pkg-config and found that .pc files are and can be listed in many places . From the manpage -
pkg-config retrieves information about packages from special
metadata files. These files are named after the package, and has a .pc
extension. On most systems, pkg-config looks in /usr/lib/pkgconfig,
/usr/share/pkgconfig, /usr/local/lib/pkgconfig and
/usr/local/share/pkgconfig for these files. It will additionally look
in the colon-separated (on Windows, semicolon-separated) list of
directories specified by the PKG_CONFIG_PATH environment variable.
- From pkg-config manpage
sure enough I saw that there are packages in /usr/lib/pkgconfig/, /usr/lib/x86_64-linux-gnu/pkgconfig/ and /usr/share/pkgconfig/ , while I can understand the /usr/local/.. part for locally compiled/built apps. I do not understand why there is a distinction between /usr/lib/pkgconfig/ and /usr/share/pkgconfig . Is it something to do with some things need to be in userspace https://en.wikipedia.org/wiki/User_space or something else entirely ?
debian libraries pkg-config
I am on Debian buster. I was reading the manpage of pkg-config and found that .pc files are and can be listed in many places . From the manpage -
pkg-config retrieves information about packages from special
metadata files. These files are named after the package, and has a .pc
extension. On most systems, pkg-config looks in /usr/lib/pkgconfig,
/usr/share/pkgconfig, /usr/local/lib/pkgconfig and
/usr/local/share/pkgconfig for these files. It will additionally look
in the colon-separated (on Windows, semicolon-separated) list of
directories specified by the PKG_CONFIG_PATH environment variable.
- From pkg-config manpage
sure enough I saw that there are packages in /usr/lib/pkgconfig/, /usr/lib/x86_64-linux-gnu/pkgconfig/ and /usr/share/pkgconfig/ , while I can understand the /usr/local/.. part for locally compiled/built apps. I do not understand why there is a distinction between /usr/lib/pkgconfig/ and /usr/share/pkgconfig . Is it something to do with some things need to be in userspace https://en.wikipedia.org/wiki/User_space or something else entirely ?
debian libraries pkg-config
asked Feb 8 at 17:28
shirish
3,26342273
3,26342273
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
The distinction is related to architecture independence. .pc
files which might be architecture-specific go in /usr/lib
(on Debian, /usr/lib/pkgconfig
for pre-multiarch packages, /usr/lib/<triplet>/pkgconfig
for multiarch packages), .pc
files which are sure to be architecture-independent can go in /usr/share
(only /usr/share/pkgconfig
, no need to distinguish triplets here).
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The distinction is related to architecture independence. .pc
files which might be architecture-specific go in /usr/lib
(on Debian, /usr/lib/pkgconfig
for pre-multiarch packages, /usr/lib/<triplet>/pkgconfig
for multiarch packages), .pc
files which are sure to be architecture-independent can go in /usr/share
(only /usr/share/pkgconfig
, no need to distinguish triplets here).
add a comment |Â
up vote
2
down vote
accepted
The distinction is related to architecture independence. .pc
files which might be architecture-specific go in /usr/lib
(on Debian, /usr/lib/pkgconfig
for pre-multiarch packages, /usr/lib/<triplet>/pkgconfig
for multiarch packages), .pc
files which are sure to be architecture-independent can go in /usr/share
(only /usr/share/pkgconfig
, no need to distinguish triplets here).
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The distinction is related to architecture independence. .pc
files which might be architecture-specific go in /usr/lib
(on Debian, /usr/lib/pkgconfig
for pre-multiarch packages, /usr/lib/<triplet>/pkgconfig
for multiarch packages), .pc
files which are sure to be architecture-independent can go in /usr/share
(only /usr/share/pkgconfig
, no need to distinguish triplets here).
The distinction is related to architecture independence. .pc
files which might be architecture-specific go in /usr/lib
(on Debian, /usr/lib/pkgconfig
for pre-multiarch packages, /usr/lib/<triplet>/pkgconfig
for multiarch packages), .pc
files which are sure to be architecture-independent can go in /usr/share
(only /usr/share/pkgconfig
, no need to distinguish triplets here).
answered Feb 8 at 17:36
Stephen Kitt
142k22308369
142k22308369
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422869%2fwhy-are-pc-files-not-listed-in-one-place%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password