The Flutter tool now generates a makefile suitable for inclusion in the main makefile that adds all the necessary plugin flags and targets. This switches to using that new system. The header copy step is removed from the plugins, since the generated makefile adds the necessary include paths. Linux plugins no longer require manual build integration, so those instructions are removed. Since there's now no need for instructions in most cases, this removes most of the plugin instructions. The sections about building plugins manually are removed since there's no evidence that people are doing manual add-to-app experimentation at this point, and it's not something that we're supporting enough to encourage it with partial instructions. The result is a much simpler set of plugin instructions, which should be more approachable.
|19 hours ago|
|.github||2 weeks ago|
|example||19 hours ago|
|plugins||19 hours ago|
|testbed||19 hours ago|
|.clang-format||1 year ago|
|.gitignore||9 months ago|
|CONTRIBUTING.md||9 months ago|
|LICENSE||2 years ago|
|README.md||1 month ago|
|analysis_options.yaml||8 months ago|
|macOS-Security.md||2 months ago|
This project was originally created to develop Windows, macOS, and Linux embeddings of Flutter. That work has since become part of Flutter; what is left here are the parts that have not yet stabilized enough to merge into the Flutter project, including:
The code here is not stable, nor intended for production use.
This project is closely tied to changes in the Flutter repository, so you must be on the latest version of the Flutter master channel. You should always update this repository and Flutter at the same time, as breaking changes for desktop happen frequently.
First you will need to enable Flutter desktop support for your platform.
flutter doctor and be sure that no issues are reported for the
sections relevant to your platform.
Once you have everything set up, just
flutter run in the
to run your first desktop Flutter application!
debug mode is currently available for Windows and Linux. Running with
--profile will succeed, but the result will still be using a
debug Flutter configuration: asserts will fire, the observatory will be enabled,
See the example README for information on using the example as a starting point to run another project.
testbed is a more complex example that is primarily intended for people
actively working on Flutter for desktop. See its README
For bug reports and feature requests specific to the example or the plugins, you can file GitHub issues. Bugs and feature requests related to desktop support in general should be filed in the Flutter issue tracker.
For general discussion and questions there's a project mailing list.