flutter/packages/flutter_tools
2019-10-18 16:35:39 -07: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 Add transitive dependencies back (#42441) 2019-10-10 12:47:34 -07:00
ide_templates/intellij Add actions and keyboard shortcut map support (#33298) 2019-06-04 11:30:24 -07:00
lib Expand scope of rethrown gradle errors (#42966) 2019-10-18 14:56:39 -07: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 Remove use_modular_headers from Podfiles using libraries (#42872) 2019-10-17 15:26:10 -07:00
test Clean up test infrastructure (#43030) 2019-10-18 16:35:39 -07: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 Unpin test and update packages (#42699) 2019-10-15 12:50:10 -07: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