Skip to content

Conversation

@jmagman
Copy link
Member

@jmagman jmagman commented Nov 5, 2020

Description

Next piece of #69334.

With the upcoming support for Apple Silicon ARM simulators, App.framework can no longer contain architectures for both iphoneos and iphonesimulator since they need to be build against different SDKs, but they can no longer be lipod together (lipo complains both binaries contain arm64 and fails).

  1. Output App.framework to different iphoneos and iphonesimulator directories (Build App.framework directly to build directory #69699)
  2. Refactor the build system to take either the iphoneos and iphonesimulator SDK from Xcode instead of trying to guess from the architectures (to stop assuming x86 == simulator). Use it for aot (Compile snapshot_assembly with sdk root set in Xcode #69731).
  3. Refactor flutter build ios-framework to pull out the universal and xcframework methods to be reused in this PR (Methods in build_ios_framework for universal and XCFrameworks #69736)
  4. Remove lipoing from debug stub framework step and only use the requested iphoneos or iphonesimulator SDK, not for both. Refactor flutter build ios-framework as needed (this PR).

Related Issues

Support #69334

@jmagman jmagman added platform-ios iOS applications specifically a: existing-apps Integration with existing apps via the add-to-app flow labels Nov 5, 2020
@jmagman jmagman self-assigned this Nov 5, 2020
@flutter-dashboard flutter-dashboard bot added tool Affects the "flutter" command-line tool. See also t: labels. work in progress; do not review labels Nov 5, 2020
@google-cla google-cla bot added the cla: yes label Nov 5, 2020
@jmagman jmagman marked this pull request as ready for review November 5, 2020 01:38
Copy link
Contributor

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fluttergithubbot
Copy link
Contributor

This pull request is not suitable for automatic merging in its current state.

  • The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label.

@jmagman
Copy link
Member Author

jmagman commented Nov 5, 2020

Those Google test failures are definitely unrelated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: existing-apps Integration with existing apps via the add-to-app flow platform-host-arm Building on an ARM-based platform platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants