[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 13:17:05 +0000

On Tue, 16 Nov 2021 at 12:23, Thomas Dickey <dickey@his.com> wrote:
> > 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?
> among other reasons:
> https://wiki.debian.org/Multiarch/Implementation

I'm confused then.  That is mostly implemented by passing --libdir and
expecting software to respect it:

"most upstream build systems (such as autoconf, with --libdir) will
install shared libraries, support files, and various development files
(such as static libraries and .so symlinks) together to the same
target directory."

For example, libxml2 is multiarch, so has its shared library in
/usr/lib/x86_64-linux-gnu in the amd64 build:


And the pkgconfig file is simply installed to $libdir/pkgconfig:


libxml2 just uses $libdir to install the pkgconfig files:


How is libxml2 doing something wrong?


reply via email to

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