dbusmenu-qt: configure failure

[bodait]

The problem seems to be with a dependency:

Error: Failed to configure dbusmenu-qt: configure failure: command execution failed

[jmroot (Joshua Root)]

Please attach the main.log which should have been mentioned in the error message.

[RJVB (René Bertin)]

Does Qt4 even install on those machines?

[RJVB (René Bertin)]

This looks more like a problem with port:qt4-mac and/or port:cmake :

114	:info:configure CMake Error at /opt/local/share/cmake-3.29/Modules/FindQt4.cmake:1314 (message):
115	:info:configure   Found unsuitable Qt version "" from NOTFOUND, this code requires Qt 4.x

Do other ports that use CMake to find Qt4 work?

Does the port still build on other (older) OS versions?

[RJVB (René Bertin)]

NB: my maintainership of this port (should have) concerned the Qt5 subport only, all the recent tinkering with the base (Qt4) version was done by the usual Qt4/KDE4 suspects...

@michaelld @nicos

[RJVB (René Bertin)]

Can't reproduce this:

> port -nok -v configure dbusmenu-qt configure.compiler=macports-clang-12
--->  Computing dependencies for dbusmenu-qt.
--->  Fetching distfiles for dbusmenu-qt
--->  Verifying checksums for dbusmenu-qt
--->  Checksumming libdbusmenu-qt-0.9.2.tar.bz2
--->  Extracting dbusmenu-qt
--->  Extracting libdbusmenu-qt-0.9.2.tar.bz2
--->  Configuring dbusmenu-qt
-- The C compiler identification is Clang 12.0.1
-- The CXX compiler identification is Clang 12.0.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/local/bin/clang-mp-12 - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/local/bin/clang++-mp-12 - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - found
-- Looking for QT_MAC_USE_COCOA
-- Looking for QT_MAC_USE_COCOA - found
-- Found Qt4: /opt/local/libexec/qt4/bin/qmake (found version "4.8.7")
-- Performing Test __DBUSMENU_HAVE_GCC_VISIBILITY
-- Performing Test __DBUSMENU_HAVE_GCC_VISIBILITY - Success
-- Performing Test __DBUSMENU_HAVE_W_OVERLOADED_VIRTUAL
-- Performing Test __DBUSMENU_HAVE_W_OVERLOADED_VIRTUAL - Success
-- Performing Test __DBUSMENU_HAVE_W_ALL
-- Performing Test __DBUSMENU_HAVE_W_ALL - Success
-- Performing Test HAVE_QICON_NAME
-- Performing Test HAVE_QICON_NAME - Success
-- Found PkgConfig: /opt/local/bin/pkg-config (found version "0.28")
-- Checking for module 'QJson>=0.5'
--   Found QJson, version 0.8.1
-- Found QJSON: /opt/local/lib/libqjson.dylib
-- QJSON found, testapp will be built
-- Configuring done (10.0s)
-- Generating done (0.1s)
CMake Warning:
  Manually-specified variables were not used by the project:
<snip>

Note though that I have my own port:qt4-mac with its own layout (that I'm not going to change/replace). I remember having my doubts on how well various Qt4 or (esp.) KDE4 ports would find their dependencies after the mainstream co-installability changes to port:qt4-mac, and have deliberately avoided to learn about any of such fallout.

Note that CMake's FindQt4.cmake says

The most important issue is that the Qt4 qmake is available via the system path. This qmake is then used to detect basically everything else.

I don't know how the mainstream port:qt4-mac names its qmake utility nor if it's on the path. CMake will consider binaries on the path called qmake qmake4 qmake-qt4 qmake-mac and verify (I think) if they're what it's looking for. If needed the port can add -DQT_QMAKE_EXECUTABLE=${qt_qmake_cmd} to configure.args. This is done by my own kde4 1.1 PortGroup but I see the mainstream PG fails to add that which is probably the reason for the current configure failure.

[RJVB (René Bertin)]

re-assigning to Nicos re: my remark about the KDE4 PortGroup above.