Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo 2 Support (Qt 5) › Compile for android fails (resource linking failed)

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #23797

    Larry

    I followed the instructions on your website here: https://felgo.com/doc/felgo-deployment-android/ and have android SDK and NDK setup correctly (SDK Version: 26.1.1, NDK Version: 19.2.5345600).  I have installed Android API’s version 21,22,29. I amusing API-21 (Android v8.0) as my minimum for my app. (Arbitrary but seems reasonable).  I have added kits for arm64-v8a and armeabi-v7a. I’m working with arm64-v8a since that matches my phone (easier for testing).

     

    My compile for android keeps failing as shown below.  I can’t figure it out.  I’m new to android so I’ve been on a serious learning curve for the last 8 hours, but can’t figure out how to fix this.

     

    I definitely reduce the number of error by moving to API 29, but still no success.  The error below relates to “-\qml\Qt” but repeating the compile causes it to error on “vplay\video” and another time on “VPlay\particles”.  The error line keeps changing!

     

    Can someone suggest what is going wrong / solution?  What is causing the file system exception at random files/points?

     

     

     

    FAILURE: Build failed with an exception.

    * What went wrong:
    Execution failed for task ‘:mergeDebugAssets’.
    > java.nio.file.FileSystemException: L:\MySimpleApp\Project\build-android-arm8-Debug\android-build\build\intermediates\merged_assets\debug\mergeDebugAssets\out\–Added-by-androiddeployqt–\qml\Qt: The parameter is incorrect.

    * Try:
    Run with –stacktrace option to get the stack trace. Run with –debug option to get more log output. Run with –scan to get full insights.

    * Get more help at https://help.gradle.org

    BUILD FAILED in 31s
    19 actionable tasks: 3 executed, 16 up-to-date
    AAPT2 aapt2-3.2.1-4818971-windows Daemon #0: shutdown
    VCS Checkout Cache (L:\MySimpleApp\Project\build-android-arm8-Debug\android-build\.gradle\vcsWorkingDirs) has not been cleaned up in 0 days
    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.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.Imagine.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.Fusion.impl
    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.Universal.impl
    Building the android package failed!
    20:54:30: The process “C:\Felgo\Felgo\android_arm64_v8a\bin\androiddeployqt.exe” exited with code 14.
    Error while building/deploying project MySimpleApp (kit: Android for arm64-v8a (Clang Qt 5.13.2 for Android ARM64-v8a))
    When executing step “Build Android APK”
    20:54:30: Elapsed time: 04:13.

     

     

    #23798

    Larry

    I thought of adding “–stacktrace” or “–debug” as suggested in the error message, but I don’t even know where I would put those…what tools causing the error…etc.

    #23799

    Larry

    Well, I’ve decided to move to MacOS for dev and testing of Android and IOS.

    Too many problems on the Windows side

Viewing 3 posts - 1 through 3 (of 3 total)

RSS feed for this thread

You must be logged in to reply to this topic.