ff4a0f676f
Support for FFI calls with `@Native external` functions through Native assets on Windows. This enables bundling native code without any build-system boilerplate code. For more info see: * https://github.com/flutter/flutter/issues/129757 ### Implementation details for Windows. Mainly follows the design of https://github.com/flutter/flutter/pull/134031. Specifically for Windows in this PR is the logic for finding the compiler `cl.exe` and environment variables that contain the paths to the Windows headers `vcvars.bat` based on `vswhere.exe`.
This directory contains templates for flutter create.
The *_shared subdirectories provide files for multiple templates.
app_sharedforappandskeleton.plugin_sharedfor (method channel)pluginandplugin_ffi.
For example, there are two app templates: app (the counter app)
and skeleton (the more advanced list view/detail view app).
┌────────────┐
│ app_shared │
└──┬──────┬──┘
│ │
│ │
▼ ▼
┌─────┐ ┌──────────┐
│ app │ │ skeleton │
└─────┘ └──────────┘
Thanks to app_shared, the templates for app and skeleton can contain
only the files that are specific to them alone, and the rest is automatically
kept in sync.