Laurent, I'm using qt4+quartz+framework as suggested. I still received the error about qt_menu.nib not being loaded, but manually copied it into the QuteCom.app/Contents/Resources directory and can now successfully build a package that executes properly.
I doubt doing a manual copy is the correct fix, but it works for me at the moment. Thanks, Scott On 9/15/11 4:11 PM, "Laurent Tarrisse" <[email protected]> wrote: >This bug is related to Qt : >https://bugreports.qt.nokia.com//browse/QTBUG-5952 > >~$ port variants qt4-mac >qt4-mac has the variants: >... > framework: Build as Frameworks >… > >It seems that Qt is not build as framework by default … >This variant was not here before. >You should install qt4 via macports with : sudo port install +quartz >+framework > >Laurent > >Le 15 sept. 2011 à 21:10, Scott Miles a écrit : > >> OK, so I removed the pre-packaged Qt4 and used the macports version as >> recommended. Still having problems.. >> >> Running the executable created from "make install" still works fine, but >> "make QuteCom-install" doesn't, as before. But I do receive a different >> error: >> >> Qt internal error: qt_menu.nib could not be loaded. The .nib file should >> be placed in QtGui.framework/Versions/Current/Resources/ or in the >> resources directory of your application bundle. >> >> >> >> I suspect this is related to these errors during the build: >> cp: /opt/local/lib/libQtCore.dylib/Versions/4/QtCore: Not a directory >> cp: /opt/local/lib/libQtGui.dylib/Versions/4/QtGui: Not a directory >> cp: /opt/local/lib/libQtXml.dylib/Versions/4/QtXml: Not a directory >> cp: /opt/local/lib/libQtSvg.dylib/Versions/4/QtSvg: Not a directory >> cp: /opt/local/lib/libQtNetwork.dylib/Versions/4/QtNetwork: Not a >>directory >> cp: /opt/local/lib/libQtDBus.dylib/Versions/4/QtDBus: Not a directory >> cp: /opt/local/lib/libQtWebKit.dylib/Versions/4/QtWebKit: Not a >>directory >> cp: QT_PHONON_LIBRARY_RELEASE-NOTFOUND/Versions/4/phonon: No such file >>or >> directory >> >> >> I've tried using the packaged Cmake 2.6.4 as well as cmake 2.8.5 from >> macports with the same issue. >> >> Here's the library references: >> >> $ otool -L QuteCom.app/Contents/MacOS/QuteCom >> QuteCom.app/Contents/MacOS/QuteCom: >> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current >>version >> 111.1.7) >> @executable_path/../Frameworks/libglib-2.0.0.dylib (compatibility >>version >> 2801.0.0, current version 2801.8.0) >> @executable_path/../Frameworks/libintl.8.dylib (compatibility version >> 10.0.0, current version 10.1.0) >> @executable_path/../Frameworks/libgmodule-2.0.0.dylib (compatibility >> version 2801.0.0, current version 2801.8.0) >> @executable_path/../Frameworks/libgthread-2.0.0.dylib (compatibility >> version 2801.0.0, current version 2801.8.0) >> >> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbo >>x >> (compatibility version 1.0.0, current version 1.0.0) >> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit >> (compatibility version 1.0.0, current version 1.0.0) >> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio >> (compatibility version 1.0.0, current version 1.0.0) >> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa >> (compatibility version 1.0.0, current version 12.0.0) >> >> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreService >>s >> (compatibility version 1.0.0, current version 32.0.0) >> >> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/Syst >>em >> Configuration (compatibility version 1.0.0, current version 212.2.0) >> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon >> (compatibility version 2.0.0, current version 136.0.0) >> >> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFound >>at >> ion (compatibility version 150.0.0, current version 476.19.0) >> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime >> (compatibility version 1.0.0, current version 1680.28.0) >> @executable_path/../Frameworks/libboost_program_options-mt.dylib >> (compatibility version 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libboost_serialization-mt.dylib >> (compatibility version 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libboost_signals-mt.dylib (compatibility >> version 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libboost_thread-mt.dylib (compatibility >> version 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libowutil.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libz.1.dylib (compatibility version >>1.0.0, >> current version 1.2.3) >> @executable_path/../Frameworks/libcurl.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libgobject-2.0.0.dylib (compatibility >> version 2801.0.0, current version 2801.8.0) >> @executable_path/../Frameworks/libiconv.2.dylib (compatibility version >> 8.0.0, current version 8.1.0) >> @executable_path/../Frameworks/libavcodec.dylib (compatibility version >> 52.0.0, current version 52.122.0) >> @executable_path/../Frameworks/libavutil.dylib (compatibility version >> 50.0.0, current version 50.43.0) >> @executable_path/../Frameworks/libavformat.dylib (compatibility version >> 52.0.0, current version 52.110.0) >> @executable_path/../Frameworks/libswscale.dylib (compatibility version >> 0.0.0, current version 0.14.1) >> /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current >> version 0.9.7) >> /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current >>version >> 0.9.7) >> @executable_path/../Frameworks/libgnutls.26.dylib (compatibility >>version >> 41.0.0, current version 41.12.0) >> @executable_path/../Frameworks/liblibpurple.dylib (compatibility >>version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libphapi.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libphapiutil.dylib (compatibility >>version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libwebcam.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libowbase.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libowsl.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> @executable_path/../Frameworks/libQtCore.4.dylib (compatibility version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtGui.4.dylib (compatibility version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtNetwork.4.dylib (compatibility >> version 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtXml.4.dylib (compatibility version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtSvg.4.dylib (compatibility version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtWebKit.4.dylib (compatibility >>version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libQtDBus.4.dylib (compatibility version >> 4.7.0, current version 4.7.4) >> @executable_path/../Frameworks/libpsiidle.dylib (compatibility version >> 0.0.0, current version 0.0.0) >> /usr/lib/libxml2.2.dylib (compatibility version 9.0.0, current version >> 9.16.0) >> /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current >>version >> 25.0.2) >> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current >>version >> 7.4.0) >> /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version >> 1.0.0) >> /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version >> 227.0.0) >> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit >> (compatibility version 45.0.0, current version 949.54.0) >> >> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Appl >>ic >> ationServices (compatibility version 1.0.0, current version 34.0.0) >> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation >> (compatibility version 300.0.0, current version 677.26.0) >> >> >> Thanks, >> Scott >> >> >> >> On 9/15/11 6:30 AM, "Laurent Tarrisse" <[email protected]> wrote: >> >>> I think that you're linking against pre-packaged Qt4 Š not sure it use >>> same compiler linker sdk than you ... >>> >>> 1/ build Qt4 with macports with quartz variant ( sudo port install >>> qt4-mac +quartz) remove current pre-packaged Qt4 before >>> >>> 2/ i never try to package debug version you should try with release >>> >>> Laurent >> >> > _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
