From cf9d81dbe0eadbadcc81b2565ce73e7eff26f982 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Mon, 4 Jul 2022 17:23:48 +0200 Subject: Switch to using libpkg-config instead of libpkgconf by default The use of (now deprecated) libpkgconf is still possible by setting config.build2.libpkgconf to true. Note that libpkgconf is known to have issues on Windows and Mac OS so this should only be used on Linux and maybe BSDs. Also note that we will only keep this until upstream (again) breaks backwards compatibility at which point we will drop this support. --- build/root.build | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'build/root.build') diff --git a/build/root.build b/build/root.build index 3afdcf9..911787f 100644 --- a/build/root.build +++ b/build/root.build @@ -49,3 +49,11 @@ using? cli # Specify the test target for cross-testing. # test.target = $cxx.target + +# Temporary ability to build with now deprecated libpkgconf instead of +# libpkg-config. Note that libpkgconf is known to have issues on Windows and +# Mac OS so this should only be used on Linux and maybe BSDs. Also note that +# we will only keep this until upstream (again) breaks backwards compatibility +# at which point we will drop this support. +# +config [bool, config.report=false] config.build2.libpkgconf ?= false -- cgit v1.1