Priority: P0: Blocker
Affects Version/s: 5.1.0 Beta 1
Fix Version/s: 5.1.0 RC1
Component/s: Packaging & Installer
I noticed that when deploying local libraries, some .dll files were copied onto my AVD (see the attached log). It turns out that there is a mix of android .so files and windows .dll files in (for example) C:\Qt\Qt5.1.0\5.1.0-beta1\android_armv7\plugins\imageformats
I guess this means that either:
1: The Windows releases of the Qt libraries for Android are being built on Windows and there's build/host/target confusion in the pro files for these plugins.
2: A build directory was re-used for both the Windows and Android builds, so the dll files were not cleaned first.
If 1: In the Necessitas days, the actual Qt libraries/plugins were always built on Linux and we only compiled the tools on Windows itself (actually, for the last 2 releases we switched to cross compiling the Windows tools on Linux with MinGW-w64 cross compilers). Maybe going the same way would safer for the 5.1.0 release? In some ways, I like the idea of compiling Qt for Android for Windows on Windows; it provides a lot of testing of the Android tools (all of them, Qt tools, Android NDK, Android SDK, mingw32-make), and ensures that we don't make incorrect assumptions.
If it's not 2: then please let me under know which environment (cmd.exe or MSYS) the Qt libraries for Windows are being compiled so I can dig into this some more.
The full list of dll files is: