Ministro invalid Qt version
-
-
-
Hello @stackprogramer,
I found no usefull solution there.
Why gives the Ministor no more inforation about the error: Maybe which version is needed, it knows this information. The app is very frugal, no icon to start, no info which version of the Qt-libs are installed on the phone...
Anyway, what astonishes me is that the QtCreator generates files with this names
QtApp-debug.apk
QtApp-debug-unaligned.apk
What the difference and why the name debug. The Creator generates this files with nearly the same size in the Debug and in the Realease bin folders.
Can it be that this both are debug version and Ministor cannot load debug-libs. -
@Andy314
hi,first sorry for wasn't useful link.second about 4 months ago i compiled my app in Qt 5.2 in mode ministro,
i was in os windows7
i download a version of ministro
https://play.google.com/store/apps/details?id=eu.licentia.necessitas.ministro&hl=en
and it works correctly.i think my app reduced about 80%.i too use QtApp-debug.apk . No both of them are not same.
app-debug-unaligned.apk = Unaligned Signed APK
app-debug.apk = Aligned Signed APK (RAM optimized using zipalign)
more info see
http://developer.android.com/tools/publishing/app-signing.html
they is related to java project android ,they are not related Qt creator and all thing i true.
if you find solving your problem please share here for futures.
thanks for attention -
I was a little bit confused about the Ministro versions. Ministro II is the newest version.
Unfortunately I have read: Whats new: Add support for Qt 5.4.
Thats the problem I use 5.5, so I must wait for a update.What do you mean? Ok, between aligned and unaligned is a different RAM model but what has it to do with signing ?
When I compile with bundle library it is surprising for me that the debug and release version of the APK have nearley the same size (8.53 and 8.52 MB). The should differ much more.