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. Qt on Mac for Android app: failed to parse default search paths from compiler output
Forum Updated to NodeBB v4.3 + New Features

Qt on Mac for Android app: failed to parse default search paths from compiler output

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
3 Posts 3 Posters 1.3k Views 2 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.
  • F Offline
    F Offline
    FranciscoSantiago
    wrote on 14 Oct 2018, 01:09 last edited by
    #1

    Hi all,

    I need the support from someone of you with more skills than me.
    I'm trying to use Qt in my mac, to create my first app for Android.
    This is the Qt version I'm using:

    Qt 5.11.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by Clang 8.1.0 (clang-802.0.42) (Apple)) on "cocoa"
    OS: macOS Sierra (10.12) [darwin version 16.7.0]

    After I set this:

    • jdk-11.jdk
    • SDK Version: 24.4.1
    • NDK Version: 18.0.5002713

    I tried to run a dummy app, and if I debug in Desktop mode I don't get any error, but if I run the Android mobile debug I get this error:

    clang++: error: unknown argument: '-mthumb-interwork'
    clang++: error: unknown argument: '-mthumb-interwork'
    Project ERROR: failed to parse default search paths from compiler output
    Error while parsing file /.../.../.../MyProject.pro. Giving up.
    

    Can someone of you help me? Where am I wronging?
    I tried to find the solution in Internet but no satisfactory answer...

    Thanks a lot!!

    1 Reply Last reply
    0
    • S Offline
      S Offline
      SGaist
      Lifetime Qt Champion
      wrote on 14 Oct 2018, 12:19 last edited by
      #2

      Hi,

      There has been many similar questions recently on this forum. The answer is basically: don't use NDK 18. The current recommended version as stated in Qt's Android Getting Started guide is r10e while people seems to have had success with version 17 as well.

      When doing Android development with 3rdparty like Qt, don't jump on the latest and greatest versions of all the dependencies. NDK updates have a tendency to break things fairly regularly.

      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
      2
      • E Offline
        E Offline
        ekkescorner
        Qt Champions 2016
        wrote on 15 Oct 2018, 08:00 last edited by
        #3

        to test Qt 5.12 Beta 1 on Android AFIK using NDK 16b works.

        ekke ... Qt Champion 2016 | 2024 ... mobile business apps
        5.15 --> 6.8 https://t1p.de/ekkeChecklist
        QMake --> CMake https://t1p.de/ekkeCMakeMobileApps

        1 Reply Last reply
        1

        1/3

        14 Oct 2018, 01:09

        • Login

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