Hello,
the conversion from -config scripts to "gpgrt-config --libdir ... module" currently requires source changes because AM_PATH_GPGME does not use gpgrt-config unless AM_PATH_GPG_ERROR was invoked previously and set $GPGRT_CONFIG.
cu Andreas
Description
Description
Details
Details
- Version
- 1.18.0
Revisions and Commits
Revisions and Commits
| rE libgpg-error | |||
| rE788f63347eda gpg-error.m4: Factor out _AM_PATH_GPGRT_CONFIG. | |||
| rM GPGME | |||
| rMabd51848bdc8 gpgme.m4: Include _AM_PATH_GPGRT_CONFIG implementation. | |||
| rM2b7fcbf2f280 m4: Update gpg-error.m4. | |||
Event Timeline
Comment Actions
I overlooked the use case of gpgme programming not using libgpg-error. This use case should be supported.
Comment Actions
I updated gpgme.m4 to include configuration of GPGRT_CONFIG.
Using this new gpgme.m4, it should work.
Using this new gpgme.m4 plus old gpg-error.m4, checking GPGRT_CONFIG is duplicated.
Using this new gpgme.m4 plus new gpg-error.me, no problem.
In the GnuPG Project, our use cases are: AM_PATH_GPGME always comes after AM_PATH_GPG_ERROR.
Please test with the use cases of AM_PATH_GPGME only.