Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

A right set of packages in SDK for Android apps



  • Hi all,

    I'd like to have the SDK packages which are needed to cover recent of earlier versions of devices running Android for apps.
    When in the Android Build SDK we, for instance, select android-28 for something, that to me means Qt Creator uses that specific package in the SDK to build the app, and we can't apply all packages all in an app each time.

    And if the latest API, say 28, will cover the prior APIs too, hence the app created by api 28 will be working properly on that and also devices running previous APIs.
    Therefore, why not just having the latest one? Disagree? Why, please?

    If you agree, so I must delete many items in my SDK below. Right?

    0_1556226753255_1.PNG


  • Moderators

    @tomy said in A right set of packages in SDK for Android apps:

    And if the latest API, say 28, will cover the prior APIs too, hence the app created by api 28 will be working properly on that and also devices running previous APIs.
    Therefore, why not just having the latest one? Disagree? Why, please?
    If you agree, so I must delete many items in my SDK below. Right?

    yes, basically its enough to always build against the lastest API level. No matter if you run on a lower API level device in the end. Note Qt's minimum API level.
    This is pretty straight forward if you do not do some JAVA coding. If you want to ensure that certain android features also work on older devices you then should use the support libraries. (But forget about those if you do not code natively).



  • @raven-worx

    Note Qt's minimum API level.

    I always select the latest possible one, for instance, for Qt 5.12.3 which is the one I'm using now, I slecet 5.12 there.

    This is pretty straight forward if you do not do some JAVA coding.

    I use QML which is in relation to JavaScript, C++, and OpenGL. I don't think using QML I may have to deal with Java. Will I have to, in this case?

    If you want to ensure that certain android features also work on older devices you then should use the support libraries. (But forget about those if you do not code natively).

    I couldn't understand it thoroughly I suppose. Will you delve into it a little more.

    One more question about my SDK list removal items:
    Within APIs, I ought to keep only those two items of level 28, which are: SDK Platform, and Sources for Android SDK, and remove the rest. But how about the items of Tools and Extras categories? Should I simply keep what is shown in the screenshot, or must I add or remove some items?


  • Moderators

    @tomy said in A right set of packages in SDK for Android apps:

    I use QML which is in relation to JavaScript, C++, and OpenGL. I don't think using QML I may have to deal with Java. Will I have to, in this case?

    Since you do not write a single line of Java code no ;)

    I couldn't understand it thoroughly I suppose. Will you delve into it a little more.

    as i said, don't mind about it, when you do not code directly with Java API. If you only use Qt API you are fine.

    Within APIs, I ought to keep only those two items of level 28, which are: SDK Platform, and Sources for Android SDK, and remove the rest. But how about the items of Tools and Extras categories? Should I simply keep what is shown in the screenshot, or must I add or remove some items?

    no need for the sources (they just take up storage space).
    Leave Tools & Extras as they are.



  • @raven-worx
    Thanks so much.

    So I shall remove all items inside the red outline in the screenshot below, right?

    0_1556274201823_1.PNG



  • I'm still waiting for the last response. :)

    So I shall remove all items inside the red outline in the screenshot below, right?

    Right, please?


  • Moderators

    @tomy
    yes you can


Log in to reply