[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses and pkgconfig install location

From: Ross Burton
Subject: Re: ncurses and pkgconfig install location
Date: Tue, 16 Nov 2021 12:17:50 +0000

On Tue, 16 Nov 2021 at 11:33, Ross Burton <ross@burtonini.com> wrote:
> That's beside the point, I'm now looking at 100 lines of non-trivial
> logic to replace what practically every other package does with just
> pkgconfigdir=${libdir}/pkgconfig.  What problems does this logic solve
> that simply using libdir is the wrong answer for?

Also, the latest logic is still broken in builds with sysroots.

In builds with sysroots it is typical to set PKG_CONFIG_LIBDIR to the
correct pkg-config search path[1], as this is a variable that
pkg-config uses to search for files.  If the search for directories
that exist fails (cf_pkg_config_path is still none) then the new
workaround/fallback doesn't execute if PKG_CONFIG_LIBDIR is set.  Thus
my environment variable for "where to look for files in this build" is
turned into the install location for pkgconfig files, which is
entirely wrong.

If I'm telling the configure scripts where to install the pkgconfig
files with --with-pkg-config-libdir, why does it insist on arguing
with me?


[1] https://autotools.io/pkgconfig/cross-compiling.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]