449f4a6673
* Update project.pbxproj files to say Flutter rather than Chromium Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright. * Update the copyright notice checker to require a standard notice on all files * Update copyrights on Dart files. (This was a mechanical commit.) * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine. Some were already marked "The Flutter Authors", not clear why. Their dates have been normalized. Some were missing the blank line after the license. Some were randomly different in trivial ways for no apparent reason (e.g. missing the trailing period). * Clean up the copyrights in non-Dart files. (Manual edits.) Also, make sure templates don't have copyrights. * Fix some more ORGANIZATIONNAMEs |
||
|---|---|---|
| .. | ||
| bin | ||
| doc | ||
| gradle | ||
| ide_templates/intellij | ||
| lib | ||
| schema | ||
| static | ||
| templates | ||
| test | ||
| tool | ||
| analysis_options.yaml | ||
| BUILD.gn | ||
| build.yaml | ||
| dart_test.yaml | ||
| pubspec.yaml | ||
| README.md | ||
Flutter Tools
Command line developer tools for building Flutter applications.
Working on Flutter Tools
Be sure to follow the instructions on CONTRIBUTING.md to set up your development environment.
Setup
First, ensure that the Dart SDK and other necessary artifacts are available by invoking the Flutter Tools wrapper script. In this directory run:
$ ../../bin/flutter --version
Running
To run Flutter Tools from source, in this directory run:
$ ../../bin/cache/dart-sdk/bin/dart bin/flutter_tools.dart
followed by command line arguments, as usual.
Analyzing
To run the analyzer on Flutter Tools, in this directory run:
$ ../../bin/flutter analyze
Testing
To run the tests in the test/ directory, first ensure that there are no
connected devices. Then, in this directory run:
$ ../../bin/cache/dart-sdk/bin/pub run test
The tests in test/integration.shard are slower to run than the tests in
test/general.shard. To run only the tests in test/general.shard, in this
directory run:
$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard
To run the tests in a specific file, run:
$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard/utils_test.dart
When running all of the tests, it is a bit faster to use build_runner. First,
set FLUTTER_ROOT to the root of your Flutter checkout. Then, in this directory
run:
$ ../../bin/cache/dart-sdk/bin/pub run build_runner test
This is what we do in the continuous integration bots.
Forcing snapshot regeneration
To force the Flutter Tools snapshot to be regenerated, delete the following files:
$ rm ../../bin/cache/flutter_tools.stamp ../../bin/cache/flutter_tools.snapshot