Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Problem when running Release on Android kit

Problem when running Release on Android kit

Scheduled Pinned Locked Moved Solved Mobile and Embedded
13 Posts 7 Posters 12.8k Views 1 Watching
  • 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.
  • M Offline
    M Offline
    moondowner
    wrote on last edited by A Former User
    #1

    I've installed latest Android SDK, NDK, Java and Ant.
    I've stated a Nexus 7 device with Genymotion, and ADB is working fine, as well as the 'Clean libs on Device' button in Run settings - when clicking it no errors occur.

    Now, when I execute run on the 'Android for x86 (GCC 4.7, Qt 5.1.0)' kit for Release build, I get the following error:

    @16:06:24: Running steps for project TestApp01...
    16:06:24: Configuration unchanged, skipping qmake step.
    16:06:24: Starting: "C:\Qt\Qt5.1.0\Tools\mingw48_32\bin\mingw32-make.exe"
    mingw32-make: Nothing to be done for 'first'.
    16:06:25: The process "C:\Qt\Qt5.1.0\Tools\mingw48_32\bin\mingw32-make.exe" exited normally.
    16:06:25: Starting: "C:\Qt\Qt5.1.0\Tools\mingw48_32\bin\mingw32-make.exe" INSTALL_ROOT="C:/Users/moondowner/AndroidTestProj/TestApp01/android" install
    makefile:1421: recipe for target 'install_itemfolder_01' failed
    mingw32-make: *** [install_itemfolder_01] Error 1
    16:06:26: The process "C:\Qt\Qt5.1.0\Tools\mingw48_32\bin\mingw32-make.exe" exited with code 2.
    Error while building/deploying project TestApp01 (kit: Android for x86 (GCC 4.7, Qt 5.1.0))
    When executing step 'Copy application data'
    16:06:26: Elapsed time: 00:02.@

    And I haven't changed anything in the .pro file, it's the same as it was generated. I used the new project wizard and chose Qt Quick 2 Application (Built-in Elements).

    Any ideas?

    1 Reply Last reply
    0
    • M Offline
      M Offline
      Moster
      wrote on last edited by
      #2

      Nexus 7 = ARMv7
      You have Qt for x86 active in your project. This definitely wont work. Those are different CPU architectures.

      1 Reply Last reply
      0
      • M Offline
        M Offline
        moondowner
        wrote on last edited by
        #3

        Tried with arm instead of x86, again the same problem. I even tried with one of the demo projects.

        @makefile:821: recipe for target 'install_target' failed
        mingw32-make: *** [install_target] Error 1
        11:23:59: The process "C:\Qt\Qt5.1.0\Tools\mingw48_32\bin\mingw32-make.exe" exited with code 2.
        Error while building/deploying project touchinteraction (kit: Android for arm (GCC 4.4.3, Qt 5.1.0))
        When executing step 'Copy application data'@

        1 Reply Last reply
        0
        • M Offline
          M Offline
          Moster
          wrote on last edited by
          #4

          Show your android configurations in the Qtcreator options

          1 Reply Last reply
          0
          • M Offline
            M Offline
            moondowner
            wrote on last edited by
            #5

            Screenshots: https://www.dropbox.com/sh/jsip7gz3stzf1q1/feucJqeyC_/qt-android#/

            1 Reply Last reply
            0
            • M Offline
              M Offline
              Moster
              wrote on last edited by
              #6

              I only tried it once on windows 7, but did you make sure that you use the x86 android NDK? Ive also been using sun java sdk 7 and not 6.

              1 Reply Last reply
              0
              • M Offline
                M Offline
                moondowner
                wrote on last edited by
                #7

                Everything is x86. I'll try with JDK7 but I think that it's not even getting to that step, I think that it's failing something with mingw32.

                I'll search if there is a make argument which I can add so that it will print in console more descriptive output when an error happens.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  moondowner
                  wrote on last edited by
                  #8

                  OK I fixed it, but not the way I wanted.

                  I installed Ubuntu, and then the standard procedure, installing Java, Ant, Android SDK and NDK and then the Qt Android setup.

                  I did the same steps, open a sample app, add Android arm kit, clicked Build and then Run, and it works.

                  1 Reply Last reply
                  0
                  • A Offline
                    A Offline
                    amilosavljevic
                    wrote on last edited by
                    #9

                    I had the same (similar) problem with Qt 5.1.1. The problem in my case was a blank character in the project/build path.
                    @23:11:50: The process "D:\Qt\Online\Tools\mingw48_32\bin\mingw32-make.exe" exited normally.
                    23:11:50: Starting: "D:\Qt\Online\Tools\mingw48_32\bin\mingw32-make.exe" INSTALL_ROOT="D:\SVN Projects\AEK\AEK\android" install
                    The system cannot find the path specified.
                    The system cannot find the path specified.
                    makefile:2552: recipe for target 'install_itemfolder_01' failed
                    mingw32-make: *** [install_itemfolder_01] Error 1
                    23:11:51: The process "D:\Qt\Online\Tools\mingw48_32\bin\mingw32-make.exe" exited with code 2.
                    Error while building/deploying project AEK (kit: Android for arm (GCC 4.8, Qt 5.1.1))
                    When executing step 'Copy application data'
                    23:11:51: Elapsed time: 00:09@

                    1 Reply Last reply
                    0
                    • T Offline
                      T Offline
                      tower120
                      wrote on last edited by
                      #10

                      Still the same error on 5.2.1. It also don't likes non English symbols in folder. (You certainly will have them in your build path, if you use localized qt version)

                      1 Reply Last reply
                      0
                      • F Offline
                        F Offline
                        farhad
                        wrote on last edited by
                        #11

                        I am new to QT. I tried running accelbubble example on my smartphone as well as the emulator for google nexus_S but got the following issue : [install_app] Error 1. When i checked the compile output it showed : @bq. @@@23:09:55: Running steps for project accelbubble...
                        23:09:55: Configuration unchanged, skipping qmake step.
                        23:09:55: Starting: "C:\Qt\Tools\mingw48_32\bin\mingw32-make.exe"
                        mingw32-make: Nothing to be done for 'first'.
                        23:09:57: The process "C:\Qt\Tools\mingw48_32\bin\mingw32-make.exe" exited normally.
                        23:09:57: Removing directory C:\Qt\5.2.1\mingw48_32\examples\sensors\build-accelbubble-Android_for_armeabi_v7a_GCC_4_8_Qt_5_2_1-Debug\android-build
                        23:09:57: Starting: "C:\Qt\Tools\mingw48_32\bin\mingw32-make.exe" INSTALL_ROOT="C:\Qt\5.2.1\mingw48_32\examples\sensors\build-accelbubble-Android_for_armeabi_v7a_GCC_4_8_Qt_5_2_1-Debug\android-build" install
                        copy /y "libaccelbubble.so" "C:\Qt\5.2.1\mingw48_32\examples\sensors\build-accelbubble-Android_for_armeabi_v7a_GCC_4_8_Qt_5_2_1-Debug\android-build\libs\armeabi-v7a\libaccelbubble.so"
                        1 file(s) copied.
                        The full path of C:C:\Qt\5.2.1\mingw48_32\examples\sensors\build-accelbubble-Android_for_armeabi_v7a_GCC_4_8_Qt_5_2_1-Debug\android-build\Qt\5.2.1\android_armv7\examples\qtsensors\accelbubble is too long.
                        makefile:852: recipe for target 'install_app' failed
                        mingw32-make: *** [install_app] Error 1
                        23:10:00: The process "C:\Qt\Tools\mingw48_32\bin\mingw32-make.exe" exited with code 2.
                        Error while building/deploying project accelbubble (kit: Android for armeabi-v7a (GCC 4.8, Qt 5.2.1))
                        When executing step 'Copy application data'
                        23:10:00: Elapsed time: 00:05.

                        1 Reply Last reply
                        0
                        • K Offline
                          K Offline
                          kornava
                          wrote on last edited by
                          #12

                          For me its fixed after deleting all the spaces in project path (in folder names)

                          1 Reply Last reply
                          0
                          • ZZZZZMLZ Offline
                            ZZZZZMLZ Offline
                            ZZZZZML
                            wrote on last edited by
                            #13

                            I met the same problem as you, I had solved the error by uninstalling two diffirent version Qt creators in my pc. Keep the last version Qt creator on my windows8.1. I tried , builded and ran, it installed successfully the apk on my android device.

                            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