Dan Field
Dan Field
IOW, it seems like it'd be very nice if the tool could do something like this: if a plugin is in dev_dependencies, ignore it unless building for a test target...
/cc @blasten @jmagman who probably know a lot more about how or if this could work on Android and iOS.
It's very similar, although I guess this one is proposing a specific solution to it that's a bit different from what I'm suggesting.
When do we re-generate the GeneratedPluginRegistrant code?
> Why would the native-side app ever need to register dev_dependencies? Because for integration_test, it has to report test results up to the native side test harness - e.g. to...
I guess that makes sense, then we would just need to exclude it from the generated plugin registrant
Raising priority on this.
@Sunbreak that's a different issue for this. This issue is about running host Dart and the Flutter tool on a Windows ARM machine. The linked issue is about creating Flutter...
We would need help from the Dart team on this, AFAIK Dart does not support Windows arm64. @rmacnak-google @a-siva or @mraleph would know better.
Adding engine label because in the event that Dart can or will support this, the engine build rules and recipes would need to be updated to handle it.