Skip to content

iOS build needs migrating to xcode "modern build system" #3293

Closed

Description

@softins

In PR #3292 we move from macos-11 to macos-12 because of the deprecation of macos-11 by Github.

In macos-12, the earliest versions of xcode available are 13.x.x. These versions fail by default if the project uses the "legacy build system".

PR #3292 includes a configuration setting to suppress the failure and deprecation warning, so that the build succeeds.

The "legacy build system" is completely removed in xcode 14, and so we need to update the iOS build to use the newer xcode "modern build system".

Activity

  1. ann0see commented on Jun 20, 2024

    @ann0see
    Member

    Do we know how to tell qt to use the modern build system?

  2. softins commented on Jun 22, 2024

    @softins
    MemberAuthor

    Do we know how to tell qt to use the modern build system?

    I don't know. Maybe Qt 6 already does so? Currently, we are still using Qt 5.15.2 for iOS.

  3. ann0see commented on Jun 22, 2024

    @ann0see
    Member

    Currently, we are still using Qt 5.15.2 for iOS.

    Yes. due to gui bugs I commented on #2711 a while ago.

  4. added this to the Release 3.12.0 milestone on Jun 29, 2024
  5. moved this from Triage to Backlog in Trackingon Jun 29, 2024
  6. added
    iOSiOS runtime issue
    toolingChanges to the automated build system
    on Jun 29, 2024
  7. pljones commented on Jun 29, 2024

    @pljones
    Collaborator

    How does this relate to #3065?

  8. ann0see commented on Jun 29, 2024

    @ann0see
    Member

    The issue to upgrade to qt6 is that qt6 has UI issues.

  9. assigned and unassigned on Jun 29, 2024
  10. pljones commented on Jun 29, 2024

    @pljones
    Collaborator

    That doesn't really help explain how the migration of xcode to a modern build system relates to using Qt6.

    We may not be able to do it because of some other issue. But neither this issue nor the PR I mention appears to be down to UI problems.

    So what I'm asking is how the two do relate.

  11. ann0see commented on Jun 30, 2024

    @ann0see
    Member

    The open question is if we can move to the new build system without needing to change to Qt 6 or if we can move to Qt6 without GUI issues.

  12. pljones commented on Jul 1, 2024

    @pljones
    Collaborator

    The open question is if we can move to the new build system without needing to change to Qt 6 or if we can move to Qt6 without GUI issues.

    That's two questions:

    • can we move to the new build system without needing to change to Qt 6
    • can we move to Qt6 without GUI issues

    The second only comes into play if the answer to the first is "No". Do we know the answer? If not, the second doesn't come into play.

  13. softins commented on Jul 1, 2024

    @softins
    MemberAuthor
    • can we move to the new build system without needing to change to Qt 6

    I don't think so, not easily. According to this page, the Qt fix to support the modern build system only appeared in 5.15 at the 5.15.6 release, which is not available free in binary form. The latest Qt 5 available free as binary is 5.15.2. For this reason, according to miurahr/aqtinstall#636 (comment), later versions of Qt 5.15 can't be installed via aqtinstall.

    I haven't yet discovered which version of Qt 6 introduced support for the modern build system.

  14. ann0see commented on Aug 7, 2024

    @ann0see
    Member

    I made some progress with the UI being at least somewhat usable. See e.g #3343

  15. linked a pull request that will close this issueUpgrade iOS Build to Qt6 #3445on Dec 26, 2024
  16. moved this from Backlog to Done in Trackingon Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    toolingChanges to the automated build system

    Type

    No type

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions