You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been adding a build for cloud init on exherbo, we've stubbled an issue with pkg-config usage. Some systems might want to build for multi-arch in their package manager, and for this, they use different pkg-config location (there are other reasons like sandboxing...). It is done without being specified in PATH to prevent wrong usage of this command, in exherbo's case.
This issue requests to considerate PKG_CONFIG environment variable as an override of the default pkg-config cloud-init build system is using.
The project seems to only usage pkg-config in setup_utils.py.
The text was updated successfully, but these errors were encountered:
This commit adds the possibility to specify a custom pkg-config binary path
in build scripts using the PKG_CONFIG environment variable. Packages
managers might use different pkg-config depending on the target platform.
FixescanonicalGH-6099
Enhancement
👋
We've been adding a build for cloud init on exherbo, we've stubbled an issue with
pkg-config
usage. Some systems might want to build for multi-arch in their package manager, and for this, they use differentpkg-config
location (there are other reasons like sandboxing...). It is done without being specified inPATH
to prevent wrong usage of this command, in exherbo's case.This issue requests to considerate
PKG_CONFIG
environment variable as an override of the defaultpkg-config
cloud-init build system is using.The project seems to only usage
pkg-config
in setup_utils.py.The text was updated successfully, but these errors were encountered: