History

Add build warning for non-debug desktop builds (#38932 )

When building in profile or release mode on desktop, add a prominent
warning that it's actually a debug build. This is to help address issues
with people being unaware of the current state of builds due to
following third-party guides rather than official documentation.

macOS is not included since PRs are in flight for macOS release support.

2019-08-20 20:16:29 -07:00

bin

Support for macOS release mode (1 of 3) (#37425 )

2019-08-15 16:36:45 -07:00

doc

Add emulatorID field to devices in daemon (#34794 )

2019-06-26 16:39:23 +01:00

gradle

Allow flavors and custom build types in host app (#36805 )

2019-07-29 09:26:41 -07:00

ide_templates/intellij

Add actions and keyboard shortcut map support (#33298 )

2019-06-04 11:30:24 -07:00

lib

Add build warning for non-debug desktop builds (#38932 )

2019-08-20 20:16:29 -07:00

schema

Adds support for generating projects that use AndroidX support libraries (#31028 )

2019-05-31 18:33:02 -07:00

static

Reland support flutter test on platform chrome (#33859 )

2019-06-05 15:27:49 -07:00

templates

Remove iphonesimulator from SUPPORTED_PLATFORMS for Profile and Release modes (#38905 )

2019-08-20 13:30:43 -07:00

test

Add build warning for non-debug desktop builds (#38932 )

2019-08-20 20:16:29 -07:00

tool

Reland "Integrate dwds into flutter tool for web support (#34252 )" (#37649 )" (#37650 )

2019-08-05 16:51:57 -07:00

analysis_options.yaml

refactor context to be implicit-downcast safe (#31622 )

2019-04-25 15:51:08 -07:00

BUILD.gn

remove bsdiff BUILD.ng (#38342 )

2019-08-12 13:04:10 -07:00

build.yaml

Reland support flutter test on platform chrome (#33859 )

2019-06-05 15:27:49 -07:00

dart_test.yaml

use pub run for create test and remove [INFO] logs (#35839 )

2019-07-10 08:48:01 -07:00

pubspec.yaml

Comparing pixels instead of bytes with GoldenFileComparator (#38473 )

2019-08-19 09:06:22 -07:00

README.md

[flutter_tool] Add some useful commands to the README.md (#36560 )

2019-07-23 09:47:06 -07:00

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

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