Qt 4.7.2 - Definitely something wrong with macdeployqt! :(

goetz

You'd better open an issue on the "bug tracker":http://bugreports.qt.nokia.com to make the guys in charge of macdeployqt aware of the problem. They might not read Qt DevNet at all. And be sure to post the issue id here, so that others can track/vote for the issue.

agarny

Volker, I am taking it that you tried (assuming you have a Mac) and that you got the same problem? Anyway, I have created a bug tracker: http://bugreports.qt.nokia.com/browse/QTBUG-17959

goetz

Nope. Although I develop for OS X too, I do not use macdeployqt. It appeared too late - we have our own set of scripts to do the same task (and some more additional work).

agarny

Because of that macdeployqt issue, I was thinking of reverting to Qt SDK 2010.05, but I like the updated Qt Creator, so I might have a look at doing the work of macdeployqt using my CMake script. Incidentally, Qt SDK 1.1 Beta doesn't seem to work nicely with CMake on Mac OS X, since the installer suggests installing the Qt SDK under one's home directory (!!) which makes CMake unable to find Qt. So far, I must confess that I am rather disappointed by Qt SDK 1.1 Beta. More problems than anything at this point.

goetz

You can always get the components of the SDK individually. That's what I do, but it is of course a matter of taste (and of habit, as there was no SDK when I started with Qt etc.)

EDIT: PS - the SDK 1.1 is still in beta test, so some problems should be expected. Unfortunately, it hit you...

agarny

Unless I am mistaken, Qt SDK 1.1 is indeed beta, but it comes with Qt Creator 2.1.0 and Qt 4.7.2, both of which are not beta. At least, that's what I remember reading somewhere when it came out earlier this week.

goetz

That's right, but there can be packaging or other errors in the SDK too. It's not just only putting a few binary packages to one big meta package.

You might be more successful if you use the individual components.

agarny

Fair point. Ok, I guess I will try to use the individual components and see how things go. It's just that it would be a pain if I have to go that route, since I develop on Windows, Ubuntu (on 3 different virtual machines) and Mac OS X. But well...

agarny

Ok, I have just uninstalled Qt SDK 1.1 Beta from my Mac and installed Qt 4.7.2 and Qt Creator 2.1.0 individually, and... everything works fine! Ok, that was painless, so I am very happy with this solution (thanks Volker for 'forcing' me into doing it!).

agarny

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

tjenssen

Sorry we as the SDK team didn't got these bugreports - so this is a communication problem. But as an advice if you see something which is working with the standalone Qt but not in the SDK please choose "Nokia Qt SDK Installer" as the project in jira.

PS: moved the bugreports to us

vulkanr

for what its worth:

macdeployqt disregards the symbolic links under the frameworks when it is copying them. therefore copying every framework binary twice and crashing at runtime
macdeployqt also fails to make a .dmg from applications which contain spaces. this is because it forks hdiutil and hands it the name splitted by ' '.

i submitted a patch for both problems under http://bugreports.qt.nokia.com/browse/QTSDK-731

hope this helps.