Well how I wrote I am not really sure about what is in my last post. I would have to try to compile QT again to really answer you. Maybe I have just problem with DirectX version... Then maybe my previous post was not really worth of reading...
Obviously you cannot use whitespaces in the project path.
I removed that one whitespace my project path contained and the 'binary operator expected' error disappeared.
However now there's still another problem:
@Invalid json file: /Users/Ju7/Workspaces/QtWorkspace/build-QtQuick2Test-Android_für_armeabi_v7a_GCC_4_7_Qt_5_2_0-Debug/android-libQtQuick2Test.so-deployment-settings.json
14:02:21: Der Prozess "/Applications/Qt/5.2.0-beta1/android_armv7/bin/androiddeployqt" wurde mit dem Rückgabewert 2 beendet.
Fehler beim Erstellen/Deployment des Projekts QtQuick2Test(Kit: Android für armeabi-v7a (GCC 4.7, Qt 5.2.0))
Bei der Ausführung von Schritt 'Deploy to Android device'@
It's because of the length of the path.
After shortening the path name it kinda works, but not quite...
It creates the package successfully
@14:13:19: Package deploy: Running command '/Applications/adt-bundle-mac-x86_64-20131030/sdk/platform-tools/adb -s HT13RTJ45542 pull /system/lib/libc.so /Users/Ju7/Workspaces/QtWorkspace/build-QtQuick2Test-Android-armeabi_v7a-Debug/libc.so'.@
and then it takes very long to proceed and I get this message
@3086 KB/s (11577012 bytes in 3.662s)@
Finally the application launches on my device but the application output returns something like:
@"starting remote process. 'org.qtproject.example.QtQuick2Test' could not launch"@
Does anyone know about this?
I actually removed Qt 5.1.1 and installed the 5.2 beta, which can be found right "here":http://download.qt-project.org/development_releases/qt/5.2/5.2.0-beta1/
Everyrhing seems to work fine now :)
Qt uses the Android NDK, which means the application is compiled to platform specific binary code. So the build for ARM will not work on x86.
I think that when you create a deployment package, it will include both architectures in the bundle, but am not sure. As on Interest mailing list or IRC. Or wait for somebody more experienced here ;)
You're welcome :)
[quote]Although I still seem to get a ton of:
failed to refresh moc step[/quote]I don't use the VS Add-In myself, so I don't know what that is. You can start a new thread to see if anyone can help you with that.