flutter/packages/flutter_tools
Jonah Williams 978fada33c
Refactor flutter.gradle to use assemble directly (#43876)
Removes multiple re-entrant calls of bundle and aot and replaces them with a single call to assemble. This restores full caching and will allow follow-up performance improvements when building multiple ABIs
2019-11-08 12:41:24 -08:00
..
bin Always embed Flutter.framework build mode version from Xcode configuration (#42029) 2019-10-15 15:33:55 -07:00
doc Add emulatorID field to devices in daemon (#34794) 2019-06-26 16:39:23 +01:00
gradle Refactor flutter.gradle to use assemble directly (#43876) 2019-11-08 12:41:24 -08:00
ide_templates/intellij Add actions and keyboard shortcut map support (#33298) 2019-06-04 11:30:24 -07:00
lib Refactor flutter.gradle to use assemble directly (#43876) 2019-11-08 12:41:24 -08:00
schema Add the beginnings of plugin support for Windows and Linux (#41015) 2019-09-26 14:01:57 -07:00
static Reland support flutter test on platform chrome (#33859) 2019-06-05 15:27:49 -07:00
templates Add v1 plugin register function into v2 plugin template (#44166) 2019-11-05 20:03:50 -08:00
test Refactor flutter.gradle to use assemble directly (#43876) 2019-11-08 12:41:24 -08:00
tool indent formal parameters correctly (#41644) 2019-10-04 11:00:18 +02:00
analysis_options.yaml [flutter_tool] Use curly braces around single statment control structures (#40446) 2019-09-13 14:51:35 -07:00
BUILD.gn Add "web" server device to allow running flutter for web on arbitrary browsers (#39951) 2019-09-10 19:29:31 -07:00
build.yaml Reland support flutter test on platform chrome (#33859) 2019-06-05 15:27:49 -07:00
dart_test.yaml Clean up test infrastructure (#43030) 2019-10-18 16:35:39 -07:00
pubspec.yaml Update packages to get latest dwds (#44344) 2019-11-07 13:15:58 -08:00
README.md Always fake ProcessManager when you fake Filesystem in tests (#42369) 2019-10-11 11:23:12 -07:00

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