public inbox for
 help / color / mirror / Atom feed
From: Eli Schwartz <>
Subject: Re: [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2
Date: Thu, 9 Jun 2022 01:52:21 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 6/3/22 1:09 AM, ~eschwartz wrote:
> From: Eli Schwartz <>
> A pkg-config file is necessary in order to robustly communicate across
> build systems that bz2 is installed, *where* it is installed, and the
> correct CFLAGS / LDFLAGS to use in order to compile and link against it.

Some distros already provide one of these, so it's currently a bit
inconsistent how to look for the library. As a result, there is software
in the wild that probes for the library name, and fails if the library
is installed to a custom prefix, and other software that checks for
pkg-config, and fails on distros that don't provide their own bzip2.pc

In general it's good to have.

And particularly, it makes it much easier to detect bzip2 as "a
dependency" instead of "manual linker flags" from the Meson build
system, which can then toggle between multiple "dependency" providers
via e.g.

Eli Schwartz

  reply	other threads:[~2022-06-09  5:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  3:45 [PATCH bzip2 1/6] install relative symlinks ~eschwartz
2022-06-03  4:20 ` [PATCH bzip2 2/6] port the build configuration to autoconf ~eschwartz
2022-06-09  5:56   ` Eli Schwartz
2022-06-03  4:48 ` [PATCH bzip2 4/6] make a couple program aliases symlinks instead of copies ~eschwartz
2022-06-03  4:54 ` [PATCH bzip2 5/6] install man page symlinks for a couple more symlinked commands ~eschwartz
2022-06-03  5:09 ` [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2 ~eschwartz
2022-06-09  5:52   ` Eli Schwartz [this message]
2022-10-23 16:03     ` Sam James
2022-06-09  4:50 ` [PATCH bzip2 3/6] shared Makefile: add install rule ~eschwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).