Remove the 'doctor' script (#402)
Almost nothing is left in this script, and most people aren't building testbed. The vcvars64.bat test should be added to `flutter doctor` shortly where it will be much more useful (in practice, that's the most common error people are hitting, and it's when running 'example', not 'testbed').
|1 day ago|
|.github/ISSUE_TEMPLATE||1 day ago|
|build/ci||3 days ago|
|example||2 days ago|
|plugins||2 days ago|
|testbed||2 days ago|
|third_party/dart_packages||3 days ago|
|tools||1 day ago|
|.appveyor.yml||3 days ago|
|.clang-format||11 months ago|
|.gitignore||3 days ago|
|.travis.yml||3 days ago|
|CONTRIBUTING.md||3 days ago|
|Debugging.md||5 days ago|
|LICENSE||1 year ago|
|Quick-Start.md||1 month ago|
|README.md||1 day ago|
|analysis_options.yaml||4 months ago|
This project was originally created to develop Windows, macOS, and Linux implementations of Flutter. That work has since become part of the Flutter engine repository, and this project is now just an example of, and test environment for, building applications using those libraries.
For information about the shells themselves, see the Flutter page about desktop support.
If you have an existing Flutter app and just want to get it running, see the quick start page before continuing.
You will need developer tools for your platform:
If you are building anything other than
example/, the tooling and build
infrastructure for this project requires that you have
a Flutter tree in the same parent directory as the clone of this project:
<parent dir> ├─ flutter (from https://github.com/flutter/flutter) └─ flutter-desktop-embedding (from https://github.com/google/flutter-desktop-embedding)
Alternately, you can place a
.flutter_location_config file in the directory
containing flutter-desktop-embedding, containing a path to the Flutter tree to
use, if you prefer not to have the Flutter tree next to
example directory contains an example application built using the library
for each platform. See its README to get started.
In addition, there is:
plugins: Plugins which provide access to additional platform functionality. These follow a similar structure to Flutter plugins. See the README for details.
third_party: Dependencies used by this repository, beyond Flutter itself.
tools: Tools used in the development process.
Debugging of the Flutter side of a desktop application is possible, but requires setup.
For bug reports and specific feature requests, you can file GitHub issues. For general discussion and questions there’s a project mailing list.
When submitting issues related to build errors or other bugs, please make sure to include the git hash of the Flutter checkout you are using. This will help speed up the debugging process.