Getting Started
Prerequisites
- Dart SDK 3.4+ — included with Flutter, or install standalone from dart.dev
- Git — required for SDK installation and contributor workflows
Installation
Install flutter_compile globally with Dart's package manager:
dart pub global activate flutter_compile
Verify the installation:
flutter_compile --version
Tip: You can also use the short alias
fcp anywhere you'd type flutter_compile.
Shell Completion
Enable tab completion for your shell:
Bash
flutter_compile completion bash >> ~/.bashrc
source ~/.bashrc
Zsh
flutter_compile completion zsh >> ~/.zshrc
source ~/.zshrc
Install Your First SDK
Install the latest stable Flutter SDK:
flutter_compile sdk install stable
The first SDK you install is automatically set as the global default. Set it explicitly with:
flutter_compile sdk global stable
Verify with:
flutter_compile sdk exec flutter doctor
Health Check
Run the doctor command to verify your environment:
flutter_compile doctor
This checks for required tools (git, python3, dart, flutter), engine tools (gclient, ninja, Xcode/Visual Studio), configuration, and contributor environments.
Quick Reference
| Task | Command |
|---|---|
| Install an SDK | fcp sdk install stable |
| List installed SDKs | fcp sdk ls |
| Set global SDK | fcp sdk global 3.24.0 |
| Pin SDK to project | fcp sdk use 3.24.0 |
| Run through SDK | fcp sdk exec flutter run |
| Remove an SDK | fcp sdk remove 3.22.0 |
| Check environment | fcp doctor |
| Show config | fcp config |
| Update CLI | fcp update |
Next Steps
- SDK Management — Deep dive into managing multiple SDKs
- Contributor Setup — Set up Flutter/engine/DevTools contributor environments
- CLI Reference — Full command reference with all flags and options
- VS Code Extension — Manage SDKs from your editor