This repository was archived by the owner on Feb 25, 2025. It is now read-only.
Don't insist on modules when attempting to include the Flutter umbrella header. #35060
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.
This fixes local engine builds on Mac. The
copy_and_verify_framework_moduleexists to ensure that the umbrella header can be cleanly imported from an ObjC
TU. However, the compile flags insist on module support being enabled. It isn't
clear how this used to work earlier since no modules were provided. Likely, this
was a race. Remove the insistence on modules because that wasn't the intent of
creating the target in the first place.
The issue fixed is the following: