gpgme 1.7.0 fails to build when Qt5 is active

[blair (Blair Zajac)]

libtool: link: ranlib .libs/libgpgmepp.a
libtool: link: ( cd ".libs" && rm -f "libgpgmepp.la" && ln -s "../libgpgmepp.la" "libgpgmepp.la" )
make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/cpp/src'
make[4]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/cpp'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/cpp'
make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/cpp'
Making all in qt
make[3]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/qt'
Making all in src
make[4]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/qt/src'
`test -f 'abstractimportjob.h' || echo './'`abstractimportjob.h -o abstractimportjob.moc
/bin/sh: abstractimportjob.h: command not found
make[4]: *** [abstractimportjob.moc] Error 127
make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/qt/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang/qt'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0/lang'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0'
make: *** [all] Error 2
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gpgme/gpgme/work/gpgme-1.7.0" && /usr/bin/make -w all 
Exit code: 2

It appears that MOC and MOC2 are not set:

$ grep MOC gpgme-1.7.0/lang/qt/src/Makefile
MOC = 
MOC2 = 
	$(MOC) `test -f '$<' || echo '$(srcdir)/'`$< -o $@

And the configure output:

checking for moc... no
checking moc version... no
checking for moc-qt5... no
checking for qtchooser... no
./configure: line 19559: qtchooser: command not found
./configure: line 19560: /moc: No such file or directory

[dbevans (David B. Evans)]

Actually it builds for me (and on the buildbots) but I don't have qt4 or qt5 installed and I'm guessing that you do. A better description of the problem seems to be that it attempts to build opportunistically with some flavor of Qt and then fails to configure properly if one exists. Otherwise it disables any Qt binding.

The configure output that I get with no Qt active is:

checking for GPGME_QT... checking for GPGME_QTTEST... ./configure: line 19267: : command not found
configure: WARNING:
***
*** Qt5 (Qt5Core) not found Qt Binding will be disabled.
***

I missed this initially. Will take a look at adding variants for building with Qt. Thanks for the report.

[dbevans (David B. Evans)]

Ok, looks like this version supports bindings for python2 python3 and qt5.

To fix your build issue quickly, I made an initial commit in r153086 which adds a missing dependency on pkgconfig and disables python and qt bindings by default.

Will add the usual python variants and one for qt5 as well over the weekend.

[mkae (Marko Käning)]

Cc Me!

[mkae (Marko Käning)]

René, I guess this is superseded by #53122, right?

[RJVB (René Bertin)]

Not really, and I think the issue was resolved already in r153086.

#53122 is in part about adding support for Qt5.

[mkae (Marko Käning)]

David, can this issue be closed then?

[dbevans (David B. Evans)]

Replying to mkae:

David, can this issue be closed then?

Yes, the originally reported failure no longer occurs although python and qt5 support are currently disabled as we all know. As René says the Qt part of #53122 addresses adding Qt5 support. Python remains to do.