Default pkg-config paths not found
Bug #1661070 reported by
Ruddick Lawrence
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
New
|
Undecided
|
Unassigned | ||
Bug Description
pkg-config has built-in paths that it searches:
$ pkg-config --variable pc_path pkg-config
/usr/local/
However, these are absolute, so they are different in a snap. This results in scripts that use pkg-config failing (such as https:/
One solution might be setting the correct default paths in the PKG_CONFIG_PATH environment variable in the wrappers (similar to how PATH is treated).
| affects: | snapcraft (Ubuntu) → snapcraft |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → Incomplete |
Revision history for this message
| Ruddick Lawrence (mrjogo) wrote | #2 |
| Changed in snapcraft: | |
| status: | Incomplete → New |
| tags: | added: robotics |
To post a comment you must log in.
we some interesting things with .pc files as pkg-config does not have a concept of only one sysroot and from the point of view of pkg-config we have at least 3; the current part's install directory, the stage directory and the root file system.
Please send over a snapcraft enabled repo as a test subject to research further.
FTR, the package config search path is set, but it does the wrong thing wrt to prefix given the sysroot situation.