Build App.framework directly to build directory #69699
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#69612 with updated
ios_content_validation_test.Description
Since #51453 we no longer need to build the App.framework to a known directory like
project/ios/Flutter/App.framework. Instead, build the frameworks directly to the build products directory. For example,flutter build ios -v --simulatorwill build to/build/ios/Debug-iphonesimulator/App.framework.Additionally, this sets us up to no longer need to
lipothe simulator and non-simulator frameworks together since they will build to different directories.flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart
Lines 103 to 112 in cb67513
When Apple Silicon ships and ARM simulators are supported, this
lipowill fail since the simulator and real device frameworks will both containarm64.Also stop copying the
.DS_Storedirectories, while we're at it (already done withFlutter.framework). These files shouldn't be copied, and it adds spew during the installation phase:Related Issues
#60118
Tests
Updated
ios_content_validation_test. Already many many integration tests that will blow up in the compiled dart code or flutter_assets are missing.