You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tool/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,9 +164,9 @@ If you need to pin a particular version, edit the table at the top of the `updat
164
164
To allow the tool to be used with a locally-built engine, the `flutter` tool accepts three
165
165
global parameters:
166
166
167
-
*`local-engine`, which specifies which build of the engine to run
168
-
*`local-engine-host`, which specifies which build of the engine to use for host artifacts like the dart compiler
169
-
*`local-engine-src-path` (optional), which specifies the path to your engine sources
167
+
-`local-engine`, which specifies which build of the engine to run
168
+
-`local-engine-host`, which specifies which build of the engine to use for host artifacts like the dart compiler
169
+
-`local-engine-src-path` (optional), which specifies the path to your engine sources
170
170
171
171
A typical invocation would be: `--local-engine=android_debug_unopt --local-engine-host=host_debug_unopt`.
172
172
@@ -197,7 +197,7 @@ If you do this, you can omit `--local-engine-src-path` and not bother to set `$F
197
197
the `flutter` tool will use these paths to determine the engine also! The tool tries really hard to
198
198
figure out where your local build of the engine is if you specify `--local-engine`.
199
199
200
-
Similar to the [dwds debugging workflow](https://github.com/dart-lang/webdev/blob/master/dwds/CONTRIBUTING.md#with-flutter-tools-recommended), the Flutter tool can also be debugged with DevTools by invoking the tool with `flutter/bin/dart --observe flutter/packages/flutter_tools/bin/flutter_tools.dart` and then using the **first** DevTools URL that is printed to the console.
200
+
Similar to the [dwds debugging workflow](https://github.com/dart-lang/webdev/blob/main/dwds/CONTRIBUTING.md#with-flutter-tools-recommended), the Flutter tool can also be debugged with DevTools by invoking the tool with `flutter/bin/dart --observe flutter/packages/flutter_tools/bin/flutter_tools.dart` and then using the **first** DevTools URL that is printed to the console.
0 commit comments