[PATCH Libgpg-error] gpg-error.m4: support pkg-config

Alon Bar-Lev alon.barlev at gmail.com
Mon Dec 3 00:12:13 CET 2018

On Mon, Dec 3, 2018 at 12:27 AM NIIBE Yutaka <gniibe at fsij.org> wrote:
> Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
> > it would be good to have a clear conversation about strategy and
> > tactics to do so.
> For pkg-config support, I think that I explained and show our way to do
> so, but it seems that my points were not accepted unfortunately.
> You can see my changes in GnuPG libraries, in the repo (master).  In
> next releases, we will provide .pc files by libgpg-error, npth,
> libgcrypt, libassuan, libksba, ntbtls, and gpgme.  Users of those
> libraries will be able to use pkg-config if they want.  Say, by using
> pkg.m4 for autoconf to generate configure script.
> For gpg-error.m4 and other m4 files, we don't have any idea to introduce
> pkg-config support in that macro file, because we don't change the build
> of GnuPG itself.
> I think that use of pkg.m4 is superior, because it supports multiple
> modules at once.
> I think that there are two different things here; pkg-config support for
> users of libraries, and change of GnuPG build.
> For the latter, it should be conservative, because GnuPG is important
> tool and it should be available earlier in the bootstrap process of
> operating system.

We are discussing here the "change of GnuPG build" to support both
modes, the proprietary config files as default and in addition
pkg-config using pkg.m4 for these who wishes to use pkg-config to
build GnuPG components. This is trivial as I showed in this patch.


More information about the Gnupg-devel mailing list