default-providers: switch pkgconfig provider to pkgconf
PATCH 1/1 default-providers: switch pkgconfig provider to pkgconf
pkg-config has been unmaintained since 2017. Major Linux distributions such as Fedora, Debian, Alpine, and Arch Linux have all switched to pkgconf as their default pkg-config implementation. Upstream projects no longer use or recommend pkg-config. There is no reason for Yocto to keep lagging behind and continue using a dead tool.
Switch the preferred providers for pkgconfig, nativesdk-pkgconfig and pkgconfig-native to pkgconf, aligning with the broader ecosystem.
---
There is also the question of the pkgconf wrappers:
https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/pkgconf/pkgconf
Should we keep making pkgconf emulate the legacy pkg-config behavior? At this point, projects have had sufficient time to adopt native pkgconf compatibility, so it may be worth dropping the wrappers and letting pkgconf behave as its own tool.
--- meta/conf/distro/include/default-providers.inc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
meta/conf/distro/include/default-providers.inc +3 -3
@@ -56,9 +56,9 @@ PREFERRED_PROVIDER_getopt ?= "util-linux-getopt" PREFERRED_PROVIDER_openssl ?= "openssl" PREFERRED_PROVIDER_openssl-native ?= "openssl-native" PREFERRED_PROVIDER_nativesdk-openssl ?= "nativesdk-openssl" -PREFERRED_PROVIDER_pkgconfig ?= "pkgconfig" -PREFERRED_PROVIDER_nativesdk-pkgconfig ?= "nativesdk-pkgconfig" -PREFERRED_PROVIDER_pkgconfig-native ?= "pkgconfig-native" +PREFERRED_PROVIDER_pkgconfig ?= "pkgconf" +PREFERRED_PROVIDER_nativesdk-pkgconfig ?= "nativesdk-pkgconf" +PREFERRED_PROVIDER_pkgconfig-native ?= "pkgconf-native" PREFERRED_RPROVIDER_initd-functions ?= "initscripts" PREFERRED_PROVIDER_nativesdk-mesa ?= "nativesdk-mesa"
Signature · 1 line
2.43.0
Quoted 9 lines · Kory Maincent via lists.openembedded.org
pkg-config has been unmaintained since 2017. Major Linux distributions such as Fedora, Debian, Alpine, and Arch Linux have all switched to pkgconf as their default pkg-config implementation. Upstream projects no longer use or recommend pkg-config. There is no reason for Yocto to keep lagging behind and continue using a dead tool.
Switch the preferred providers for pkgconfig, nativesdk-pkgconfig and pkgconfig-native to pkgconf, aligning with the broader ecosystem.
I’ve been working on this migration during this cycle and literally last night did one last built of the universe with pkgconfig vs pkgconf. It’s not quite as simple as just switching the providers, but it’s close.
Quoted 4 lines
Should we keep making pkgconf emulate the legacy pkg-config behavior? At this point, projects have had sufficient time to adopt native pkgconf compatibility, so it may be worth dropping the wrappers and letting pkgconf behave as its own tool.
This is a bigger question. The pkgconf maintainers have Opinions on how —variable and sysroots interact and simply dropping the fdo behaviour does result in build breakage.
Ross
Hello Ross,
Quoted 9 lines · On Tue, 17 Mar 2026 13:37:48 +0000 Ross Burton <[email protected]> wrote:
Quoted 7 lines · Kory Maincent via lists.openembedded.org
pkg-config has been unmaintained since 2017. Major Linux distributions such as Fedora, Debian, Alpine, and Arch Linux have all switched to pkgconf as their default pkg-config implementation. Upstream projects no longer use or recommend pkg-config. There is no reason for Yocto to keep lagging behind and continue using a dead tool.
Quoted 6 lines
Quoted 2 lines
Switch the preferred providers for pkgconfig, nativesdk-pkgconfig and pkgconfig-native to pkgconf, aligning with the broader ecosystem.
I’ve been working on this migration during this cycle and literally last night did one last built of the universe with pkgconfig vs pkgconf. It’s not quite as simple as just switching the providers, but it’s close.
Oh, great!
Quoted 8 lines
Quoted 4 lines
Should we keep making pkgconf emulate the legacy pkg-config behavior? At this point, projects have had sufficient time to adopt native pkgconf compatibility, so it may be worth dropping the wrappers and letting pkgconf behave as its own tool.
This is a bigger question. The pkgconf maintainers have Opinions on how —variable and sysroots interact and simply dropping the fdo behaviour does result in build breakage.
I know it will raise some discussion, but maybe we could align with Buildroot choice on this topic:
https://github.com/buildroot/buildroot/blob/master/package/pkgconf/0001-Only-prefix-with-the-sysroot-a-subset-of-variables.patch
Regards,
Signature · 3 lines
Köry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com
Quoted 32 lines · Kory Maincent via lists.openembedded.org
Hello Ross,
Quoted 9 lines · On Tue, 17 Mar 2026 13:37:48 +0000 Ross Burton <[email protected]> wrote:
Quoted 7 lines · Kory Maincent via lists.openembedded.org
pkg-config has been unmaintained since 2017. Major Linux distributions such as Fedora, Debian, Alpine, and Arch Linux have all switched to pkgconf as their default pkg-config implementation. Upstream projects no longer use or recommend pkg-config. There is no reason for Yocto to keep lagging behind and continue using a dead tool.
Quoted 5 lines
Quoted 2 lines
Switch the preferred providers for pkgconfig, nativesdk-pkgconfig and pkgconfig-native to pkgconf, aligning with the broader ecosystem.
I’ve been working on this migration during this cycle and literally last night did one last built of the universe with pkgconfig vs pkgconf. It’s
not
Quoted 1 line
quite as simple as just switching the providers, but it’s close.
Oh, great!
Quoted 2 lines
Quoted 2 lines
Should we keep making pkgconf emulate the legacy pkg-config behavior? At this point, projects have had sufficient time to adopt native
pkgconf
Quoted 5 lines
Quoted 2 lines
compatibility, so it may be worth dropping the wrappers and letting pkgconf behave as its own tool.
This is a bigger question. The pkgconf maintainers have Opinions on how —variable and sysroots interact and simply dropping the fdo behaviour
Quoted 10 lines
does
Quoted 1 line
result in build breakage.
I know it will raise some discussion, but maybe we could align with Buildroot
choice on this topic:
Whats upstreams view on this patch ? it seems that it will be custom from distro to distro. I wonder if upstream could consider an option to add a list of such dirs via envvar or some other mechanism to insert it.
Quoted 17 lines
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#233324):
https://lists.openembedded.org/g/openembedded-core/message/233324
Mute This Topic: https://lists.openembedded.org/mt/118362272/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-