Repository navigation
Split develop, deploy and profile builds for both iOS and Android in flutter tool #2366
Description
- android flutter build/run --debug (JIT)
- android flutter build/run --profile (AOT)
- android flutter build/run --release (AOT)
- android, ensure that --profile and --release are not available for emulators (fail better when running --profile or --release against android emulators #4197)
- ios flutter build/run --debug (interpreter) (Need a development workflow for iOS Devices #2042)
- ios flutter build/run --profile (AOT)
- ios flutter build/run --release (AOT)
- ios, ensure that --profile and --release are not available for simulators (ensure that --profile and --release are not available for ios simulators #4200)
- modes accessible from atom (can choose which mode to run in) (How to configure release mode with Atom plugin? #4042)
- it's possible to take a screenshot from a simulator/emulator w/o the slow mode banner
more docs on the modes are here: https://github.com/flutter/flutter/wiki/Flutter's-modes
develop:
- very fast edit/refresh
- Checked mode is possible
- Interpreted or JITed (device vs. simulator, possible we'll want to use interpreter in both places when possible)
- Observatory enabled.
profile:
- Checked mode code removed
- Ahead of time compiled (AOTC) when possible
- Observatory enabled.
deploy:
- checked mode removed
- ATOC
- Observatory removed.
We don't have to actually make the configs different to begin with, but we do need to expose this difference in the flutter tool in order to make space for the backend work (like wiring in the Interpreter mode on iOS develop on devices).
Activity
sethladd commentedon Mar 3, 2016
This may be implied but develop mode enables fast edit/refresh cycles.
On Thu, Mar 3, 2016, 9:00 AM Eric Seidel [email protected] wrote:
devoncarew commentedon Mar 3, 2016
Is the profile build configuration necessary?
deploywould work for profiling modulo the removal of the observatory.This would mean we don't pass things like
--checkedintorun(orbuild), we pass--deployor--dev.I'm going to assume that dev mode and deploy mode would likely load their assets (images and code) in different ways. Dev mode may be a shell we build with any native code, but where the dart code is sideloaded (and re-loaded). The deploy mode would AOT it all into one binary, deployable artifact.
abarth commentedon Mar 3, 2016
The difference is whether to include observatory (binary size) and whether to have the sampling profiler running (battery). If you don't have a profiling build, you either need to pay the costs of the devtools/profiler in production or not be able to profile the production configuration.
eseidelGoogle commentedon Mar 14, 2016
#2042 tracks the iOS build support necessary for this tooling.
devoncarew commentedon Apr 18, 2016
The current names are
develop,profile, anddeploy. Do people have preferences re: renaming the modes, to either:debug,profile,deploydebug,profile,releasedevoncarew commentedon Apr 18, 2016
I'm working on a PR which would rename to
debug,profile,deploy.Hixie commentedon Apr 18, 2016
Searching google for [debug release] and [debug deploy] suggests the first pair is more widely used.
sethladd commentedon May 11, 2016
How close are we to closing this? Do we have a checklist of remaining items?
Two related items:
#3269 (build and upload gen_snapshot to darwin-x64)
#3827 (document the various modes)
devoncarew commentedon May 25, 2016
@chinmaygarde, @tvolkert, I re-purposed this bug as a burndown of the remaining items. Can you update the ios related ones (listed in the very first entry in the bug)? Thanks!
chinmaygarde commentedon May 25, 2016
I updated the entries. Thanks.
devoncarew commentedon May 26, 2016
@chinmaygarde, I updated based on some testing, and filed #4200 (re: --profile and --release against simulators).
abarth commentedon Jan 27, 2017
Done.
[connecitivity_macos] Fix warnings to publish (flutter#2366)
github-actions commentedon Aug 16, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.