Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Android development on MacOS with Qt Creator 4.9.2?
Forum Updated to NodeBB v4.3 + New Features

Android development on MacOS with Qt Creator 4.9.2?

Scheduled Pinned Locked Moved Solved General and Desktop
macosmacosxandroidandroid emulato
23 Posts 4 Posters 5.5k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T ThanksForTheHelp
    31 Jul 2019, 09:50

    Well... I need x86_64 since I am going to develop my app for a Samsung Galaxy S10? Wouldn't switching kits to, for example armeabi-v7a, a problem?

    J Offline
    J Offline
    J.Hilk
    Moderators
    wrote on 31 Jul 2019, 09:54 last edited by
    #6

    @thanksforthehelp are you sure its a 64 bit x86 architecture?

    Because as far as I know, those do not come precompiled, only the 32 bit one.

    So you would have to build Qt yourself for that one.


    Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


    Q: What's that?
    A: It's blue light.
    Q: What does it do?
    A: It turns blue.

    1 Reply Last reply
    0
    • T Offline
      T Offline
      ThanksForTheHelp
      wrote on 31 Jul 2019, 10:01 last edited by
      #7

      From the looks of it on this website it seems as if Galaxy S10 and S10+ both have 64 bit processors. My guess is that I need x86_64 development for that. I can have x86 but wouldn't that be inefficient and sloppy?

      J J 2 Replies Last reply 31 Jul 2019, 10:04
      0
      • T ThanksForTheHelp
        31 Jul 2019, 10:01

        From the looks of it on this website it seems as if Galaxy S10 and S10+ both have 64 bit processors. My guess is that I need x86_64 development for that. I can have x86 but wouldn't that be inefficient and sloppy?

        J Offline
        J Offline
        J.Hilk
        Moderators
        wrote on 31 Jul 2019, 10:04 last edited by
        #8

        @thanksforthehelp
        please check your device settings to make sure :)
        0_1564567437467_b2544a5b-778e-4767-a50f-e39506886df7-image.png

        I can have x86 but wouldn't that be inefficient and sloppy?

        32 bit apps run fine on 64 bit systems, in 90% of all cause you won't notice or measure a difference


        Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


        Q: What's that?
        A: It's blue light.
        Q: What does it do?
        A: It turns blue.

        1 Reply Last reply
        1
        • T ThanksForTheHelp
          31 Jul 2019, 10:01

          From the looks of it on this website it seems as if Galaxy S10 and S10+ both have 64 bit processors. My guess is that I need x86_64 development for that. I can have x86 but wouldn't that be inefficient and sloppy?

          J Offline
          J Offline
          jsulm
          Lifetime Qt Champion
          wrote on 31 Jul 2019, 10:08 last edited by
          #9

          @thanksforthehelp said in Android development on MacOS with Qt Creator 4.9.2?:

          My guess is that I need x86_64 development for that

          No, Galaxy S10 and S10+ have ARM CPUs, not x86.
          As @J-Hilk shows you need ARM64-v8a

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          1 Reply Last reply
          1
          • T Offline
            T Offline
            ThanksForTheHelp
            wrote on 31 Jul 2019, 10:13 last edited by
            #10

            Instruction Sets: arm64-v8a
            Kernel Architecture: aarch64
            CPU Architecture: ARMv8-A

            Does that mean 32 bit? I sure as heck looks like 64 since it doesn't say 32

            J J 2 Replies Last reply 31 Jul 2019, 10:17
            0
            • T ThanksForTheHelp
              31 Jul 2019, 10:13

              Instruction Sets: arm64-v8a
              Kernel Architecture: aarch64
              CPU Architecture: ARMv8-A

              Does that mean 32 bit? I sure as heck looks like 64 since it doesn't say 32

              J Offline
              J Offline
              jsulm
              Lifetime Qt Champion
              wrote on 31 Jul 2019, 10:17 last edited by jsulm
              #11

              @thanksforthehelp CPU supports 64bit, but is able to execute 32bit as far as I know. Just like Windows/Linux on 64bit machines.

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • T Offline
                T Offline
                ThanksForTheHelp
                wrote on 31 Jul 2019, 10:19 last edited by
                #12

                I know 64 bit computer are able to execute and run 32 bit programs. The issue, as far as I can understand, is that 32 bit programs tend to be a bit slower since they do not utilise the whole CPU or something. Even if the difference is, for example, 90% performance I do not want 32 bit build because I need and want as fast, secure and stable as possible.

                1 Reply Last reply
                0
                • T ThanksForTheHelp
                  31 Jul 2019, 10:13

                  Instruction Sets: arm64-v8a
                  Kernel Architecture: aarch64
                  CPU Architecture: ARMv8-A

                  Does that mean 32 bit? I sure as heck looks like 64 since it doesn't say 32

                  J Offline
                  J Offline
                  J.Hilk
                  Moderators
                  wrote on 31 Jul 2019, 10:32 last edited by
                  #13

                  @thanksforthehelp
                  well there you have it, select your Qt for Android ARM64-v8a kit
                  and you should be good to go


                  Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                  Q: What's that?
                  A: It's blue light.
                  Q: What does it do?
                  A: It turns blue.

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    ThanksForTheHelp
                    wrote on 31 Jul 2019, 10:33 last edited by
                    #14

                    I managed to solve the initial error:

                    Initializing deployment to Android device/simulator
                    Error while building/deploying project untitled (kit: Android for x86_64 (Clang Qt 5.13.0 for Android x86_64))
                    When executing step "Deploy to Android device"```
                    
                    by opening Android Studio -> SDK Manger -> Tick Show Package Details -> Install Android 9.+ (Q) with Atom_64 -> apply -> install.
                    
                    Now when I compile a Google Pixel 2 XL pops up when I run but no app is created. There are errors in the 'Issues' tab:
                    

                    :-1: error: error: cannot find -lc++
                    :-1: error: linker command failed with exit code 1 (use -v to see invocation)

                    J 1 Reply Last reply 31 Jul 2019, 10:36
                    0
                    • T Offline
                      T Offline
                      ThanksForTheHelp
                      wrote on 31 Jul 2019, 10:35 last edited by ThanksForTheHelp
                      #15

                      Selecting Qt for Android ARM64-v8a does not compile. There are no supported ABIs for that on my computer nor in the SDK manager...

                      Edit: Entering the AVD Manager and changing the architecture of my default phone emulator mirror/profile on other images ATM to nougat 25 for arm64-v8a target build android 7.1.1, despite me having android 9.0, lets try it out

                      1 Reply Last reply
                      0
                      • T ThanksForTheHelp
                        31 Jul 2019, 10:33

                        I managed to solve the initial error:

                        Initializing deployment to Android device/simulator
                        Error while building/deploying project untitled (kit: Android for x86_64 (Clang Qt 5.13.0 for Android x86_64))
                        When executing step "Deploy to Android device"```
                        
                        by opening Android Studio -> SDK Manger -> Tick Show Package Details -> Install Android 9.+ (Q) with Atom_64 -> apply -> install.
                        
                        Now when I compile a Google Pixel 2 XL pops up when I run but no app is created. There are errors in the 'Issues' tab:
                        

                        :-1: error: error: cannot find -lc++
                        :-1: error: linker command failed with exit code 1 (use -v to see invocation)

                        J Offline
                        J Offline
                        J.Hilk
                        Moderators
                        wrote on 31 Jul 2019, 10:36 last edited by
                        #16

                        ah @thanksforthehelp different error :) would have been good to know from the beginning x)

                        take a look here
                        https://forum.qt.io/topic/103713/error-cannot-find-lc-qt-5-12-android

                        error comes from the ndk 20 despite what the docs says, that isn't quite without issues. But fixable, like the thread describes.


                        Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


                        Q: What's that?
                        A: It's blue light.
                        Q: What does it do?
                        A: It turns blue.

                        1 Reply Last reply
                        1
                        • T Offline
                          T Offline
                          ThanksForTheHelp
                          wrote on 31 Jul 2019, 11:16 last edited by
                          #17

                          It is still trying to boot the first emulation on the new architecture. I get a warning though: "Running a x86 based AVD is 10x faster". It is still trying to boot it after 5 minutes...

                          J 1 Reply Last reply 31 Jul 2019, 11:20
                          0
                          • T ThanksForTheHelp
                            31 Jul 2019, 11:16

                            It is still trying to boot the first emulation on the new architecture. I get a warning though: "Running a x86 based AVD is 10x faster". It is still trying to boot it after 5 minutes...

                            J Offline
                            J Offline
                            jsulm
                            Lifetime Qt Champion
                            wrote on 31 Jul 2019, 11:20 last edited by
                            #18

                            @thanksforthehelp said in Android development on MacOS with Qt Creator 4.9.2?:

                            "Running a x86 based AVD is 10x faster"

                            Yes, for testing in VM on PC it is better to use x86 based AVD as it is way slower to emulate complete different CPU (ARM on x86).

                            https://forum.qt.io/topic/113070/qt-code-of-conduct

                            1 Reply Last reply
                            0
                            • T Offline
                              T Offline
                              ThanksForTheHelp
                              wrote on 31 Jul 2019, 11:21 last edited by
                              #19

                              @jsulm so I should deploy for x86 but then when I have my prototype complete I build it with arm? Should the final product, besides the binary files, work the same and be the same?

                              J 1 Reply Last reply 31 Jul 2019, 11:22
                              0
                              • T ThanksForTheHelp
                                31 Jul 2019, 11:21

                                @jsulm so I should deploy for x86 but then when I have my prototype complete I build it with arm? Should the final product, besides the binary files, work the same and be the same?

                                J Offline
                                J Offline
                                jsulm
                                Lifetime Qt Champion
                                wrote on 31 Jul 2019, 11:22 last edited by
                                #20

                                @thanksforthehelp Yes, exactly. But you should still test on a ARM based phone/emulator sometimes :-)

                                https://forum.qt.io/topic/113070/qt-code-of-conduct

                                1 Reply Last reply
                                1
                                • T Offline
                                  T Offline
                                  ThanksForTheHelp
                                  wrote on 31 Jul 2019, 11:58 last edited by
                                  #21

                                  After switching to x86 and applying the fix to remove the new compiler errors mentioned above I get a fully running emulation of android. When does my program actually boot? Have selected android x86 project, stacked, but nothing happens after the phone boots up...

                                  1 Reply Last reply
                                  0
                                  • T Offline
                                    T Offline
                                    ThanksForTheHelp
                                    wrote on 31 Jul 2019, 12:22 last edited by
                                    #22

                                    Never mind! The program starts after about 1 minute 30 seconds, I just have to wait without pressing the emulated screen/phone

                                    1 Reply Last reply
                                    0
                                    • S Offline
                                      S Offline
                                      Surajkumar Tanurkar
                                      wrote on 11 Apr 2020, 11:45 last edited by
                                      #23

                                      Screenshot 2020-04-11 at 5.13.33 PM.png

                                      i am getting this error
                                      i am using,

                                      Qt Creator 4.11.2
                                      Based on Qt 5.14.2 (Clang 10.0 (Apple), 64 bit)

                                      Built on Mar 27 2020 02:24:45

                                      From revision 699407b4ba

                                      Copyright 2008-2020 The Qt Company Ltd. All rights reserved.

                                      The program is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

                                      Android Studio 3.6.2
                                      please help
                                      i am not able to create build for android in qt
                                      thanks!!!!!

                                      1 Reply Last reply
                                      0

                                      • Login

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Users
                                      • Groups
                                      • Search
                                      • Get Qt Extensions
                                      • Unsolved