Qt 4.7.2 - Definitely something wrong with macdeployqt

After installing Qt SDK 1.1 Beta (I am only interested in Qt Creator 2.1.0 and Qt 4.7.2), I have been experiencing some problems with my application. I have now established the cause of the problem: macdeployqt.

Here is a very simple reproducible scenario:

1. Create a new folder;
2. Create a file called Test.pro with the following contents (notice that webkit has been added to the default core and gui components:
   Code:

   ---

   QT += core gui webkit
    
   TARGET = Test
   TEMPLATE = app
    
   SOURCES += main.cpp

   ---

3. Create a file called main.cpp with the following contents:
   Code:

   ---

   #include <QApplication>
   #include <QWebView>
    
   int main(int argc, char *argv[])
   {
       QApplication a(argc, argv);
    
       QWebView w;
    
       w.show();
    
       return a.exec();
   }

   ---

4. From the terminal, do the following:
   Quote:

   ---

   $ qmake

   ---

   Everything is fine here. So, let's build our application:
   Quote:

   ---

   $ make
   g++ -c -pipe -O2 -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.5 -Wall -W -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/Developer/QtSDK/Desktop/Qt/472/gcc/mkspecs/default -I. -I/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtCore.framework/Versions/4/Headers -I/Developer/QtSDK/Desktop/Qt/472/gcc/include/QtCore -I/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtGui.framework/Versions/4/Headers -I/Developer/QtSDK/Desktop/Qt/472/gcc/include/QtGui -I/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtWebKit.framework/Versions/4/Headers -I/Developer/QtSDK/Desktop/Qt/472/gcc/include/QtWebKit -I/Developer/QtSDK/Desktop/Qt/472/gcc/include -I. -F/Developer/QtSDK/Desktop/Qt/472/gcc/lib -o main.o main.cpp
   g++ -headerpad_max_install_names -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.5 -o Test.app/Contents/MacOS/Test main.o -F/Developer/QtSDK/Desktop/Qt/472/gcc/lib -L/Developer/QtSDK/Desktop/Qt/472/gcc/lib -framework QtWebKit -framework QtGui -framework QtCore

   ---

   Things are still fine, so we can try running our test application:
   Quote:

   ---

   $ open Test.app

   ---

   As expected, everything is fine: our test application opens and runs without any problem. So, let's get it ready for deployment by using macdeployqt:
   Quote:

   ---

   $ macdeployqt Test.app
   ERROR: file copy failed from "/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtGui.framework/Resources/qt_menu.nib/classes.nib"
   ERROR: to "Test.app/Contents/Frameworks/QtGui.framework/Resources/qt_menu.nib/classes.nib"
   ERROR: file copy failed from "/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtGui.framework/Resources/qt_menu.nib/info.nib"
   ERROR: to "Test.app/Contents/Frameworks/QtGui.framework/Resources/qt_menu.nib/info.nib"
   ERROR: file copy failed from "/Developer/QtSDK/Desktop/Qt/472/gcc/lib/QtGui.framework/Resources/qt_menu.nib/keyedobjects.nib"
   ERROR: to "Test.app/Contents/Frameworks/QtGui.framework/Resources/qt_menu.nib/keyedobjects.nib"

   ---

   Amazingly enough, despite the above error messages, the reported files have been properly copied! Anyway, let's carry on and try to run our test application:
   Quote:

   ---

   $ open Test.app

   ---

   Unfortunately, this time round, we get a message box that reads:
   Quote:

   ---

   Test quit unexpectedly.
   Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.
   <Ignore> <Report...> <Reopen>

   ---

This is most frustrating, but now if you remove webkit from our Test.pro file, i.e.

Code:

---

QT += core gui
 
TARGET = Test
TEMPLATE = app
 
SOURCES += main.cpp

---

and have our main.cpp file to read:

Code:

---

#include <QApplication>
#include <QMainWindow>
 
int main(int argc, char *argv[])
{
    QApplication a(argc, argv);
 
    QMainWindow w;
 
    w.show();
 
    return a.exec();
}

---

then, macdeployqt still generates the aforementioned error messages, but at least the resulting application still works.

Now, could someone confirm all of the above? If what I am reporting was to be proven correct, then there is definitely something wrong with macdeployqt, and I will see about reporting this to the trolls.

Otherwise, I couldn't help but notice that, as a result of macdeployqt, two sets of QtCore and QtGui binaries are deployed: one under Test.app/Contents/Frameworks/QtXXX.framework/Versions/4 and another under Test.app/Contents/Frameworks/QtXXX.framework/Versions/Current. Other Qt components only have Test.app/Contents/Frameworks/QtXXX.framework/Versions/4, but QtWebKit (i.e. in the failing scenario) has Test.app/Contents/Frameworks/QtXXX.framework/Versions/Current! Gosh, things really seem to be messed up in this version of macdeployqt. :mad:

I have posted the same message on the Qt Developer Network forum and it would seem that this is a bug. So, I have filed it here.

For what it is worth, the problem still hasn’t been fixed in the final release of Qt SDK 1.1. :(

yes , I also meet such problem , and I didn't know why , and tried to find the answers , but still failed . do you guys already find the solutions for this ? If you have , please let me know , thanks very much

I am using Qt Creator 2.1.0 and Qt libraries 4.7.4. I can confirm that this problem still exists. Guess I'll have to manually do what macdeployqt does so it doesn't mess up the application.