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. V-play project for android build fail
QtWS25 Last Chance

V-play project for android build fail

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
3 Posts 3 Posters 670 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.
  • G Offline
    G Offline
    gotronics
    wrote on last edited by
    #1

    I am getting below messages whenever I try to build V-PLAY project for android sdk

    15:46:21: Running steps for project App...
    15:46:21: Configuration unchanged, skipping qmake step.
    15:46:21: Starting: "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe"
    mingw32-make: Nothing to be done for 'first'.
    15:46:22: The process "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" exited normally.
    15:46:22: Removing directory C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build/assets
    15:46:30: Removing directory C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build/libs
    15:46:31: Starting: "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" "INSTALL_ROOT=C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build" install
    C:\V-PlaySDK\V-Play\android_armv7\bin\qmake.exe -install qinstall C:\Users\tinas\Documents\Android_App\App\assets C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build\assets\assets
    C:\V-PlaySDK\V-Play\android_armv7\bin\qmake.exe -install qinstall -exe libApp.so C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build\libs\armeabi-v7a\libApp.so
    15:46:34: The process "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" exited normally.
    15:46:34: Starting: "C:\V-PlaySDK\V-Play\android_armv7\bin\androiddeployqt.exe" --input C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-libApp.so-deployment-settings.json --output C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-build --deployment bundled --android-platform android-28 --jdk "C:/Program Files/Java/jdk1.8.0_181" --gradle
    Generating Android Package
    Input file: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-libApp.so-deployment-settings.json
    Output directory: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-build/
    Application binary: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/libApp.so
    Android build platform: android-28
    Install to device: No

    FAILURE: Build failed with an exception.

    • What went wrong:
      A problem occurred configuring root project 'android-build'.

    No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android

    • Try:
      Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
      -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/iconengines/libqsvgicon.so. It has unmet dependencies: lib/libQt5Svg.so.
      -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/imageformats/libqsvg.so. It has unmet dependencies: lib/libQt5Svg.so.
      -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/position/libqtposition_serialnmea.so. It has unmet dependencies: lib/libQt5SerialPort.so.

    BUILD FAILED

    Total time: 11.382 secs
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Material.impl
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.impl
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Fusion.impl
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Imagine.impl
    Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Universal.impl
    Building the android package failed!
    -- For more information, run this command with --verbose.
    15:47:32: The process "C:\V-PlaySDK\V-Play\android_armv7\bin\androiddeployqt.exe" exited with code 14.
    Error while building/deploying project App (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.11.1 Android armv7 V-Play))
    When executing step "Build Android APK"
    15:47:32: Elapsed time: 01:11.

    main file code:

    #include <QApplication>
    #include <VPApplication>

    #include <QQmlApplicationEngine>

    int main(int argc, char *argv[])
    {
    QApplication app(argc, argv);
    VPApplication vplay;

    // Use platform-specific fonts instead of V-Play's default font
    vplay.setPreservePlatformFonts(true);
    
    QQmlApplicationEngine engine;
    vplay.initialize(&engine);
    
    // use this during development
    // for PUBLISHING, use the entry point below
    

    //vplay.setMainQmlFileName(QStringLiteral("qml/Main.qml"));

    // use this instead of the above call to avoid deployment of the qml files and compile them into the binary with qt's resource system qrc
    // this is the preferred deployment option for publishing games to the app stores, because then your qml files and js files are protected
    // to avoid deployment of your qml files and images, also comment the DEPLOYMENTFOLDERS command in the .pro file
    // also see the .pro file for more details
    vplay.setMainQmlFileName(QStringLiteral("qrc:/qml/Main.qml"));
    
    engine.load(QUrl(vplay.mainQmlFileName()));
    
    return app.exec();
    

    }

    project file code:

    allows to add DEPLOYMENTFOLDERS and links to the V-Play library and QtCreator auto-completion

    CONFIG += v-play

    uncomment this line to add the Live Client Module and use live reloading with your custom C++ code

    for the remaining steps to build a custom Live Code Reload app see here: https://v-play.net/custom-code-reload-app/

    #CONFIG += v-play-live

    configure the bundle identifier for iOS

    PRODUCT_IDENTIFIER = com.yourcompany.wizardEVAP.App

    qmlFolder.source = qml
    #DEPLOYMENTFOLDERS += qmlFolder # comment for publishing

    assetsFolder.source = assets
    DEPLOYMENTFOLDERS += assetsFolder

    Add more folders to ship with the application here

    RESOURCES += resources.qrc # uncomment for publishing

    NOTE: for PUBLISHING, perform the following steps:

    1. comment the DEPLOYMENTFOLDERS += qmlFolder line above, to avoid shipping your qml files with the application (instead they get compiled to the app binary)

    2. uncomment the resources.qrc file inclusion and add any qml subfolders to the .qrc file; this compiles your qml files and js files to the app binary and protects your source code

    3. change the setMainQmlFile() call in main.cpp to the one starting with "qrc:/" - this loads the qml files from the resources

    for more details see the "Deployment Guides" in the V-Play Documentation

    during development, use the qmlFolder deployment because you then get shorter compilation times (the qml files do not need to be compiled to the binary but are just copied)

    also, for quickest deployment on Desktop disable the "Shadow Build" option in Projects/Builds - you can then select "Run Without Deployment" from the Build menu in Qt Creator if you only changed QML files; this speeds up application start, because your app is not copied & re-compiled but just re-interpreted

    The .cpp file which was generated for your project. Feel free to hack it.

    SOURCES += main.cpp

    android {
    ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android
    OTHER_FILES += android/AndroidManifest.xml android/build.gradle
    }

    ios {
    QMAKE_INFO_PLIST = ios/Project-Info.plist
    OTHER_FILES += $$QMAKE_INFO_PLIST

    }

    set application icons for win and macx

    win32 {
    RC_FILE += win/app_icon.rc
    }
    macx {
    ICON = macx/app_icon.icns
    }

    A 1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      You should contact the VPlay folks on their forum.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      1
      • G gotronics

        I am getting below messages whenever I try to build V-PLAY project for android sdk

        15:46:21: Running steps for project App...
        15:46:21: Configuration unchanged, skipping qmake step.
        15:46:21: Starting: "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe"
        mingw32-make: Nothing to be done for 'first'.
        15:46:22: The process "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" exited normally.
        15:46:22: Removing directory C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build/assets
        15:46:30: Removing directory C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build/libs
        15:46:31: Starting: "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" "INSTALL_ROOT=C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build" install
        C:\V-PlaySDK\V-Play\android_armv7\bin\qmake.exe -install qinstall C:\Users\tinas\Documents\Android_App\App\assets C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build\assets\assets
        C:\V-PlaySDK\V-Play\android_armv7\bin\qmake.exe -install qinstall -exe libApp.so C:\Users\tinas\Documents\Android_App\build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release\android-build\libs\armeabi-v7a\libApp.so
        15:46:34: The process "C:\V-PlaySDK\Tools\mingw530_32\bin\mingw32-make.exe" exited normally.
        15:46:34: Starting: "C:\V-PlaySDK\V-Play\android_armv7\bin\androiddeployqt.exe" --input C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-libApp.so-deployment-settings.json --output C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-build --deployment bundled --android-platform android-28 --jdk "C:/Program Files/Java/jdk1.8.0_181" --gradle
        Generating Android Package
        Input file: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-libApp.so-deployment-settings.json
        Output directory: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/android-build/
        Application binary: C:/Users/tinas/Documents/Android_App/build-App-Android_for_armeabi_v7a_GCC_4_9_Qt_5_11_1_Android_armv7_V_Play-Release/libApp.so
        Android build platform: android-28
        Install to device: No

        FAILURE: Build failed with an exception.

        • What went wrong:
          A problem occurred configuring root project 'android-build'.

        No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android

        • Try:
          Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
          -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/iconengines/libqsvgicon.so. It has unmet dependencies: lib/libQt5Svg.so.
          -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/imageformats/libqsvg.so. It has unmet dependencies: lib/libQt5Svg.so.
          -- Skipping C:/V-PlaySDK/V-Play/android_armv7/plugins/position/libqtposition_serialnmea.so. It has unmet dependencies: lib/libQt5SerialPort.so.

        BUILD FAILED

        Total time: 11.382 secs
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Extras.Private.CppUtils
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Material.impl
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.impl
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Fusion.impl
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Imagine.impl
        Warning: QML import could not be resolved in any of the import paths: QtQuick.Controls.Universal.impl
        Building the android package failed!
        -- For more information, run this command with --verbose.
        15:47:32: The process "C:\V-PlaySDK\V-Play\android_armv7\bin\androiddeployqt.exe" exited with code 14.
        Error while building/deploying project App (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.11.1 Android armv7 V-Play))
        When executing step "Build Android APK"
        15:47:32: Elapsed time: 01:11.

        main file code:

        #include <QApplication>
        #include <VPApplication>

        #include <QQmlApplicationEngine>

        int main(int argc, char *argv[])
        {
        QApplication app(argc, argv);
        VPApplication vplay;

        // Use platform-specific fonts instead of V-Play's default font
        vplay.setPreservePlatformFonts(true);
        
        QQmlApplicationEngine engine;
        vplay.initialize(&engine);
        
        // use this during development
        // for PUBLISHING, use the entry point below
        

        //vplay.setMainQmlFileName(QStringLiteral("qml/Main.qml"));

        // use this instead of the above call to avoid deployment of the qml files and compile them into the binary with qt's resource system qrc
        // this is the preferred deployment option for publishing games to the app stores, because then your qml files and js files are protected
        // to avoid deployment of your qml files and images, also comment the DEPLOYMENTFOLDERS command in the .pro file
        // also see the .pro file for more details
        vplay.setMainQmlFileName(QStringLiteral("qrc:/qml/Main.qml"));
        
        engine.load(QUrl(vplay.mainQmlFileName()));
        
        return app.exec();
        

        }

        project file code:

        allows to add DEPLOYMENTFOLDERS and links to the V-Play library and QtCreator auto-completion

        CONFIG += v-play

        uncomment this line to add the Live Client Module and use live reloading with your custom C++ code

        for the remaining steps to build a custom Live Code Reload app see here: https://v-play.net/custom-code-reload-app/

        #CONFIG += v-play-live

        configure the bundle identifier for iOS

        PRODUCT_IDENTIFIER = com.yourcompany.wizardEVAP.App

        qmlFolder.source = qml
        #DEPLOYMENTFOLDERS += qmlFolder # comment for publishing

        assetsFolder.source = assets
        DEPLOYMENTFOLDERS += assetsFolder

        Add more folders to ship with the application here

        RESOURCES += resources.qrc # uncomment for publishing

        NOTE: for PUBLISHING, perform the following steps:

        1. comment the DEPLOYMENTFOLDERS += qmlFolder line above, to avoid shipping your qml files with the application (instead they get compiled to the app binary)

        2. uncomment the resources.qrc file inclusion and add any qml subfolders to the .qrc file; this compiles your qml files and js files to the app binary and protects your source code

        3. change the setMainQmlFile() call in main.cpp to the one starting with "qrc:/" - this loads the qml files from the resources

        for more details see the "Deployment Guides" in the V-Play Documentation

        during development, use the qmlFolder deployment because you then get shorter compilation times (the qml files do not need to be compiled to the binary but are just copied)

        also, for quickest deployment on Desktop disable the "Shadow Build" option in Projects/Builds - you can then select "Run Without Deployment" from the Build menu in Qt Creator if you only changed QML files; this speeds up application start, because your app is not copied & re-compiled but just re-interpreted

        The .cpp file which was generated for your project. Feel free to hack it.

        SOURCES += main.cpp

        android {
        ANDROID_PACKAGE_SOURCE_DIR = $$PWD/android
        OTHER_FILES += android/AndroidManifest.xml android/build.gradle
        }

        ios {
        QMAKE_INFO_PLIST = ios/Project-Info.plist
        OTHER_FILES += $$QMAKE_INFO_PLIST

        }

        set application icons for win and macx

        win32 {
        RC_FILE += win/app_icon.rc
        }
        macx {
        ICON = macx/app_icon.icns
        }

        A Offline
        A Offline
        ambershark
        wrote on last edited by
        #3

        @gotronics said in V-play project for android build fail:

        No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android

        This means you don't have a toolchain installed with your android developer kit that can handle the mips64el target. You need to install that if you want to target that particular architecture.

        I don't know anything about vplay to know if it truly needs that or if it can be built without it or not, that's a good question for them. :)

        My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog

        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