Page MenuHome GnuPG

AM_PATH_GPGME requires preceding invocation of AM_PATH_GPG_ERROR
Testing, HighPublic

Description

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

Details

Version
1.18.0

Event Timeline

gniibe triaged this task as High priority.

I overlooked the use case of gpgme programming not using libgpg-error. This use case should be supported.

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.

gniibe mentioned this in Unknown Object (Event).Nov 21 2022, 5:19 AM

Hello,

thank you, works for me.

cu Andreas

gniibe changed the task status from Open to Testing.Nov 29 2022, 3:41 AM