15e524a10e
Buildroot only offers two possible runtime modes for Flutter that are automatically selected based on what the user has selected: - debug if BR2_ENABLE_RUNTIME_DEBUG is enabled. - release if BR2_ENABLE_RUNTIME_DEBUG is not enabled. However, Flutter also offers the profile runtime mode option. From https://docs.flutter.dev/testing/build-modes: ``` "Use profile mode when you want to analyze performance." What is profile mode? Some debugging ability is maintained in profile mode, which is enough to profile your app's performance. Profile mode is turned off on the emulator and simulator because their behavior does not represent actual performance. ``` As Flutter projects can be heavy and consume many resources, it is necessary to allow users developing a Flutter application to profile their application during development. This patch introduces a new choice: FLUTTER_ENGINE_RUNTIME_MODE_PROFILE. If unselected, the global option BR2_ENABLE_RUNTIME_DEBUG continues to determine whether to build Flutter in release or debug mode. This new option may confuse some users who wonder where the release and debug options are, so the help menu section under the FLUTTER_ENGINE_RUNTIME_MODE_PROFILE option explains that the global BR2_ENABLE_RUNTIME_DEBUG option controls the debug and release modes. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .checkpackageignore | ||
| .clang-format | ||
| .defconfig | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches