qt4-mac/qscintilla updates and new behavior

Petr Vanek petr at scribus.info
Sun Oct 24 12:28:50 PDT 2010


hi all,

after some bugfixes we are able to install almost anything related to qt4 4.7. But when I try to rebuild my apps with qscintilla, I'm getting really strange behavior (cmake based apps which worked perfectly before). Env: fresh macports, fully patched snow leopard (upgraded from leopard month ago).

Example: output of cmake

-- Libs (cmake found): 
        /opt/local/lib/libQtCore.dylib
        /opt/local/lib/libQtGui.dylib
        /opt/local/lib/libQtXml.dylib
        /opt/local/lib/libQtNetwork.dylib
        /opt/local/lib/libqscintilla2.dylib 

...
make, linking
/usr/bin/c++    -Wl,-search_paths_first -headerpad_max_install_names  ...obj files removed... 
    -o juffed.app/Contents/MacOS/juffed  libjuff.a
    /opt/local/lib/libQtCore.dylib /opt/local/lib/libQtGui.dylib 
    /opt/local/lib/libQtXml.dylib /opt/local/lib/libQtNetwork.dylib     
   /opt/local/lib/libqscintilla2.dylib 
... linked successfully...

and now the issue:
rimmer:build-bundle pvanek$ otool -L juffed.app/Contents/MacOS/juffed 
juffed.app/Contents/MacOS/juffed:
        /opt/local/lib/libQtCore.4.dylib (compatibility version 4.7.0, current version 4.7.0)
        /opt/local/lib/libQtGui.4.dylib (compatibility version 4.7.0, current version 4.7.0)
        /opt/local/lib/libQtXml.4.dylib (compatibility version 4.7.0, current version 4.7.0)
        /opt/local/lib/libQtNetwork.4.dylib (compatibility version 4.7.0, current version 4.7.0)
	libqscintilla2.5.dylib (compatibility version 5.4.0, current version 5.4.1)
        /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)

why is the libqscintilla2.5.dylib listed without the full path? It breaks the next bundling scripts.

thanks,
petr



More information about the macports-dev mailing list