Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Update: Forum Guidelines & Code of Conduct

    Solved Can no longer define target architecture for iOS in Qt 5.8

    Mobile and Embedded
    2
    5
    1536
    Loading More Posts
    • 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.
    • A
      Andreas E. last edited by

      Hi,

      I develop an iOS app that uses an external library which only supports arm64. In Qt 5.7 I added

      QMAKE_IOS_DEVICE_ARCHS = arm64

      in the .pro file and it worked fine.

      In Qt 5.8 the linker complaints about missing symbols for armv7 for the library symbols. How can I disable armv7 in a Qt 5.8 build?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • SGaist
        SGaist Lifetime Qt Champion last edited by

        Hi and welcome to devnet,

        Looks like a potential regression. You should take a look at the bug report system to see if it's something known.

        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 Reply Quote 1
        • A
          Andreas E. last edited by

          Yes I got a response in the bug tracker.
          Apparently it has been renamed to QMAKE_APPLE_DEVICE_ARCHS in Qt 5.8. That solves the problem.
          Thanks!

          1 Reply Last reply Reply Quote 2
          • SGaist
            SGaist Lifetime Qt Champion last edited by

            Thanks for sharing your findings !

            Can you also share the link to the bug report please ?

            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 Reply Quote 0
            • A
              Andreas E. last edited by

              This is the corresponding bug report:
              https://bugreports.qt.io/browse/QTBUG-59405

              1 Reply Last reply Reply Quote 2
              • First post
                Last post