New gpg-error-config can parse (simpler) *.pc file. It can be used for other software.
For *-config command, new gpg-error-config can be used, directly, or indirectly.
Example:
* libassuan-config can call gpg-error-config, having libassuan.pc
* Or, libassuan.m4 can be modified using gpg-error-config, instead of libassuan-config
Migration plan:
* For libksba, libgcrypt and libassuan
- update gpg-error.m4 from master
- provide *.pc
- fix *-config to be compatible to pkg-config way
- modify *.m4 to use gpg-error-config
- [optionally?] modify *-config to wrap gpg-error-config
* Test with ntbtls, which uses libksba, libgcrypt, and libgpg-error
- ntbtls also provides ntbtls.pc
- modify ntbtls.m4
Future
- [optionally] we can remove *-config script and only have gpg-error-config
NPTH?
- npth doesn't depend on libgpg-error
- providing npth.pc is good
- use of gpg-error-config in npth.m4 is considered OK
Eventually:
- In major use case(s), we won't need --with-*-prefix option to configure software