Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-23904

Problems using correct NDK with Qt 5.12

    XMLWordPrintable

Details

    • Bug
    • Resolution: Invalid
    • P2: Important
    • None
    • Qt Creator 4.12.0
    • Android Support
    • None
    • Windows

    Description

      I am using Qt Creator with Qt 5.12.8 for Android. I have setup a working SDK and NDK 18, everything was working fine with QtC 4.11.

       

      Now, Qt Creator is indicating that not all necessary packages are installed. When I let QtC install these packages, it creates a "ndk_bundle" folder inside the sdk path. And it tries to use NDK v21 for Qt 5.12.8 -> which does not work. -> Bug#1.

      Since I don't need NDK v21 for now, I deleted the ndk_bundle folder inside the SDK. After restarting QtC, I can then nicely add my custom NDK as I did before. At the end, I now have an auto-detected Kit again that uses my NDK v18 for building Android apps. But here is another issue: The auto-detected Kit does not use the debugger from the custom ndk -> Bug#2.

      So I thought: Let's disable auto-detection of Android Kits, there's a nice new checkbox for it! After disabling the checkbox, I restarted Qt Creator. But the Auto-detected Kit is still there. I think when unchecking the box, auto-detected Android Kits should disappear but they don't -> Bug#3.

      Hmpf ... So I thought it should be possible to get rid of the auto-detected Android Kit. I have one more outdated Android Kit in my list that comes from somewhen in the past. It should be possible to remove invalid, autodetected Kits but this isn't possible (and has never been)! -> Bug#4.

      So let's find the related settings file for Qt Creator. It's called profiles.xml in the config folder. For testing, I just renamed the file so QtC can rebuild this file from scratch. And yeeha, my old, non-working toolchain has disappeared. However, Qt Creator did again auto-detect an Android toolchain for Qt 5.12.8. And again, it selects my NDKv18, but it doesn't select the debugger coming with this NDKv18. So re-detecting Android Kits even if this was disabled in the settings is Bug#5.

      It is possible to work around this by just cloning the android kit and manually selecting compilers and debuggers. But having obsolete, non working kits in the list just is not really nice in the long term ...

      Anyhow, assam: I like the new additions to QtC for Android very much, these are big improvements to before, especially selecting an NDK per Kit and the auto-download. The whole thing just needs some fine-tuning to better work with Qt 5.12 IMHO 

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            assam Assam Boudjelthia
            markus.maier Markus Haberlander
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes