OK, I am back again.
In the meantime I understood - thanks to an advice from Ian Wadham - that the configure option
could be used when building QT4.
In the configure options setup I also found that
was actually set which always produced both lib versions being very likely the reason for unintended linking between release and debug library version, eventually being responsible for the crashing debug version of the application under test...
So, I changed the configure options now to
@configure.args-append -debug -no-separate-debug-info@
I can verify that now only debug versions of the respective QT libs are installed:
But above you can see that all debug libraries have the extension "_debug".
When I try to build other applications using QT4 (here kdelibs4) I therefore run into other trouble:
:info:build cd /opt/macports-test/var/macports/build/_Users_marko_WC_MacPorts_ports_kde_kdelibs4/work/build/kdecore && /opt/macports-test/bin/automoc4 /opt/macports-test/var/macports/build/_Users_marko_WC_MacPorts_ports_kde_kdelibs4/work/build/kdecore/kauth_backend_plugin_automoc.cpp /opt/macports-test/var/macports/build/_Users_marko_WC_MacPorts_ports_kde
work/build/kdecore /opt/macports-test/bin/moc /opt/macports-test/bin/cmake:info:build dyld: Library not loaded: /opt/macports-test/lib/libQtCore.4.dylib
:info:build Referenced from: /opt/macports-test/bin/automoc4
:info:build Reason: image not found
:info:build /bin/sh: line 1: 82423 Trace/BPT trap /opt/macports-test/bin/automoc4 /opt/macports-test/var/macpo
orts/build/_Users_marko_WC_MacPorts_ports_kde_kdelibs4/work/build/kdecore /opt/macports-test/bin/moc /opt/macports-test
Above you can see that the build process of kdelibs4 expects to find libQtCore.4.dylib which, of course, cannot be found in my current setup.
I am wondering what can be done to make cmake build QT4 a debug version without appending the "_debug" prefix to the library names.