issues after installed qt4-mac+debug

[Ryan Schmidt]

On Jul 26, 2014, at 5:12 AM, René J.V. Bertin wrote:

> After installing the qt4-mac debug variant and rebuilding/upgrading a number of ports, I'm facing issues with the _debug libraries. As long as I keep the debug variant activated there are errors about symbols being present twice (in the regular and _debug libraries) and the only way to prevent (KDE) applications from crashing is to force the use of the DYLD _debug suffix. After deactivating the qt4-mac debug variant, it turns out that quite a few dylibs were built referring to the _debug framework content, which of course are no longer present, for example, when trying to start /opt/local/bin/kwalletd:
> 
> {{{
> dyld: Library not loaded: /opt/local/Library/Frameworks/QtCore.framework/Versions/4/QtCore_debug
>  Referenced from: /opt/local/lib/libqgpgme.1.dylib
>  Reason: image not found
> }}}
> 
> To make things less easy than it could:
> 
> {{{
> port provides /opt/local/lib/libqgpgme.1.dylib
> /Volumes/Debian/MacPorts/lib/libqgpgme.1.dylib is not provided by a MacPorts port.
> }}}
> 
> which is probably due to the fact my /opt/local is a symlink ...
> 
> I presume I could do a `ln -s Qt* /opt/local/Library/Frameworks/Qt*.framework/Versions/4/Qt*_debug` etc. on a case-by-case basis, in hope the situation will sort itself out (dyld resolves symlinks before storing 'rpath' dependencies) but that's not really elegant.
> 
> Any thoughts/pointers?

Well the obvious solutions are:

* don't use the +debug variant of qt4-mac, and
* don't make /opt/local a symlink