Details
-
Epic
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.7, 6.8
-
None
-
Android Deploy Qt re-factoring
-
Description
Who
As Android developer
As Qt for Android developer
What
I want deployment tool
- that is non-monolithic code
- that is easier to maintain i.e. to support new features
- that is more robust i.e. it is tested as well
- that is simpler than current 2.5KLOC
- that has less and clearer dependencies to Qt Creator
- we have an option to do necessary ties with CMake only approach (throw ADQt to trash bin)
Why
To make our life easier
- Future proof for upcoming features
- Faster and less work for maintenance changes
- Being more modular
- Better performance on build, deployment and signing (ie. features that ADQt offers)
When
Qt 6.7 or 6.8
Attachments
Issue Links
- covers
-
QTCREATORBUG-28972 Make Qt Creator respect Gradle's product flavors names
- Reported
-
QTBUG-123858 androiddeployqt does not consider split APKs and cannot sign them
- Reported
-
QTBUG-106959 Warnings during android build: unresolved qml import path to QtQuick.Controls.Windows and QtQuick.Controls.macOS
- Reported
-
QTBUG-115241 Android Deploy Qt tool does not copy templates and libc++_shared library in aux mode
- Closed
(2 mentioned in)