Skip to content

Commit 18fdfb8

Browse files
gspencergoogHixie
authored andcommitted
Removed 'pub get' from the instructions (flutter#3774)
* Removed 'pub get' from the instructions According to Hixie, 'pub get' is abstracted into flutter packages upgrade, and so there shouldn't be a need to run pub get directly. * Removed pub get lines entirely.
1 parent cfe70e0 commit 18fdfb8

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

CONTRIBUTING.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,6 @@ explicit `--local-engine-src-path` pointing at the `engine/src` directory. Make
101101
sure you have a device connected over USB and debugging enabled on that device:
102102

103103
* `cd /path/to/flutter/examples/hello_world`
104-
* `pub get`
105104
* `../../bin/flutter run --local-engine-src-path /path/to/engine/src --local-engine=android_debug_unopt` or `--local-engine=android_debug_unopt_x64`
106105

107106
If you put the `engine` and `flutter` directories side-by-side, you can skip the
@@ -132,7 +131,6 @@ to test the engine.
132131

133132
Once the artifacts are built, you can start using them in your application by following these steps:
134133
* `cd /path/to/flutter/examples/hello_world`
135-
* `pub get`
136134
* `../../bin/flutter run --local-engine-src-path /path/to/engine/src --local-engine=ios_debug_unopt` or `--local-engine=ios_debug_sim_unopt` for simulator
137135
* If you are debugging crashes in the engine, you can connect the `LLDB` debugger from `Xcode` by opening `ios/Runner.xcworkspace` and starting the application by clicking the Run button (CMD + R).
138136
* To debug non crashing code, open Xcode with `ios/Runner.xcworkspace`, expand Flutter->Runner->Supporting Files->main.m in the Runner project. Put a breakpoint in main() then set your desired breakpoint in the engine in [lldb](https://lldb.llvm.org/tutorial.html) via `breakpoint set -...`.

0 commit comments

Comments
 (0)