Android: qmake creates install-target rules for static libs

When building a TEMPLATE = lib project with CONFIG += staticlib, qmake generates an install-target rule in the makefile for copying the resulting .a file to $(INSTALL_ROOT)/.../$(TARGET), and the install rule makes use of this.

I doubt there is a use case for this behavior for Android. The problem is that it leads to the static lib ending up in the APK when using the recommended deployment procedure or Qt Creator. But the static lib will never be needed in the deployed package. It just increases file size.

For reference,

• the Linux install-target rule has an addition $(RANLIB) step.
• the MinGW makefile does not have an install-target rule.

If this behaviour of qmake is to be kept, androiddeployqt and/or Qt Creator may need to be modified.