Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.3.0 Beta1
-
None
-
Linux
-
-
c0e94dd0933c549f35d05318cdcd97572c61fabf
Description
When building Qt for Android configured with "-prefix ..." and "-make tools", "make install" does not use the given prefix for qttools which are built for the target system (Qt Assistant etc.). Instead it tries to install them to $(INSTALL_ROOT)/libs/$$ANDROID_TARGET_ARCH/. This leads to failure for an unprivileged user and empty INSTALL_ROOT.
I would expect to see these binaries (.so) installed to the same prefix as the other target binaries.
(Note: This configuration works in cross-development for Windows on Linux and allows to build Qt Assistant for later deployment to Windows.)
My analysis:
- The non-standard target install path comes from mkspecs/features/android, if !android_app && android_install.
- mkspecs/android-g++/qmake.conf does not set android_app but android_install.
- android_app is set in mkspecs/features/java.prf and in mkspecs/unsupported/android-g++/qmake.conf [!].
I guess these mkspecs result in the intented behaviour when deploying apps which use Qt but they misbehave when installing apps which are part of Qt.
Either this should be fixed, or these tools should not be build/installed for Android.
Attachments
Issue Links
- is duplicated by
-
QTBUG-44347 Android Build: wrong path for qdbus
- Closed
-
QTBUG-45095 make install tries to copy library to "/libs" without prefix
- Closed
-
QTBUG-52918 Sometimes INSTALL_ROOT is undefined in Makefile
- Closed
-
QTBUG-47453 '-prefix' path ignored on Android configure with qttools component
- Closed
-
QTBUG-53842 make install fails
- Closed
-
QTBUG-39300 QMAKE generates wrong install command for Android library (target.path wrong?)
- Closed
-
QTBUG-48134 Different installation problems when using Qt5.5 or ~dev
- Closed
- is replaced by
-
QTBUG-56331 Qt for Android source package tries to install to /lib
- Closed
- resulted in
-
QTBUG-61635 [5.9.1 snapshot] Cannot build for Android target
- Closed