Why?

Cause

• Minimize the complexity of the first time setup, and simplifying the process especially for Android Studio users who are not used to these tools, especially if we want to have this offering more attractive.

Customer

• Found from Qt hackathon participants, and from my testing.

Cruft

• This would not be needed as users should be able follow our installation instructions to use tools from Qt installation.

What?

Qt Quick for Android project require multiple external tools to do any build, atm JDK, Ninja, CMake and the NDK. Sometimes users don't necessarily have all of those installed from Qt side for one reason or another and issues can arise from that and logs are not always straightforward and clear to pinpoint the root cause.

There are some options that we can adopt to improve this:

• Be more helpful with the logs, for example, if the NDK is not found, instead of only saying the NDK doesn’t exist, we could start giving suggestions to install it, etc.​
• The same for CMake, if not installed, suggest to install it from Android Studio (not recommended?) or Qt Maintenance Tool. (preferred one?)​
• Use the JDK shipped by Android Studio (or the one that Qt uses??).