mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
792e26df95
To implement windows-arm64 support, it is needed to add architecture as a subdirectory (https://github.com/flutter/flutter/issues/129805). In short, when performing a flutter windows build, we have: - Before: build/windows/runner/Release/gallery.exe - After: build/windows/x64/runner/Release/gallery.exe This convention follows what flutter linux build does. Addresses: https://github.com/flutter/flutter/issues/129805 Addresses: https://github.com/flutter/flutter/issues/116196 Design doc: [flutter.dev/go/windows-arm64](https://flutter.dev/go/windows-arm64) |
||
|---|---|---|
| .. | ||
| app | ||
| app_integration_test/integration_test | ||
| app_shared | ||
| app_test_widget/test | ||
| cocoapods | ||
| module | ||
| package | ||
| plugin | ||
| plugin_ffi | ||
| plugin_shared | ||
| skeleton | ||
| xcode/ios/custom_application_bundle | ||
| README.md | ||
| template_manifest.json | ||
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.