On 17 Mar 2026, at 11:24, Kory Maincent via lists.openembedded.org <[email protected]> wrote: > > 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. > 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#233323): https://lists.openembedded.org/g/openembedded-core/message/233323 Mute This Topic: https://lists.openembedded.org/mt/118362272/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
