Description

macOS variants of #59209 and #59044 and the CocoaPods linking part of #70224

• Move macOS Podfile logic into the tool so changes can be easily made without the user needing to migrate or regenerate their Podfile.
• Parse .flutter-plugins-dependencies instead of the old .flutter-plugins to only embed the macos-enabled plugins via CocoaPods.
• Move the Flutter search path and linking behavior out of CocoaPods by generating a "fake" FlutterMacOS.podspec that doesn't point to a real framework (see Move Flutter.framework to build directory instead of ios/Flutter #70224 for how the same thing is done for iOS). This is necessary because plugin podspecs contain s.dependency 'FlutterMacOS' and CocoaPods will try to download it from the CoocaPods trunk if the Podfile doesn't pod 'FlutterMacOS', :path => relative/file. This has the advantage of making the Podfile.lock stable so :path: Flutter/ephemeral/.symlinks/flutter/darwin-x64-release becomes :path: Flutter/ephemeral/ and doesn't change if you run in different build modes, so can be checked into the user's repo if desired.
• Search path and linking is now handled by adding build settings in the Podfile via the podhelper.rb. Plugins will now link on the frameworks in the artifact cache. This means the engine artifacts don't need to be symlinked and referred to by CocoaPods, which could have been hairy if any codesigning or (future) ARM thinning actually edited these files.
• Remove now-unused FLUTTER_FRAMEWORK_DIR build setting.
• Show warning to tell user to regenerate their Podfile

Related Issues

Fixes #46618
#59044
#71953
#70735
One fewer instance of #48918

Tests

Updated plugin_lint_mac