commit | 77dacb00187497d10d17fcffa91aa6027cfa5b3a | [log] [tgz] |
---|---|---|
author | Sean Gillen <sdgillen@google.com> | Fri Jul 24 17:33:34 2020 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jul 24 17:33:34 2020 +0000 |
tree | 1d1814f8e96a86eabcc05c8e71f3aa2b396b4091 | |
parent | 34570b712d801ec0524c91a875d39a29b66afaf6 [diff] |
[benchmarks] Add flutter-driver option to scroll-flutter Previously, flutter_driver support was added using flutter_driver_extendable in BUILD.gn. However, this is only effective on debug builds of Fuchsia. We want to be able to use this for automated tests in release builds, so replace it with an explicit command-line argument that enables flutter_driver in the scroll-flutter app and set product = false in BUILD.gn to force a non-release Flutter build. Bug: 55832 Test: Manually tested in FEMU with a WIP benchmark; this appears to allow it to use flutter_driver even on release builds of Fuchsia, where previously it was only usable on debug builds. Removing the --flutter-driver argument when launching the app causes the attempt to use flutter_driver to fail in the same way the previous version did on release builds. Change-Id: If75287205774996eb27921147e72c6984a8bca69 Reviewed-on: https://fuchsia-review.googlesource.com/c/experiences/+/409634 Reviewed-by: Nathan Rogers <nathanrogers@google.com> Testability-Review: Nathan Rogers <nathanrogers@google.com> Commit-Queue: Sean Gillen <sdgillen@google.com>
This is a companion repository to Fuchsia and contains code that either implements or supports user facing code for the Fuchsia platform. The code provides a majority of the user interface for the Workstation product as well as a small set of examples, tests, and benchmarks.
This repository is a “source petal” included in the Fuchsia Platform Source Tree (FPST) checkout. Code in this repository must be built with Fuchsia in order to be functional, see (the guide)[https://fuchsia.dev/fuchsia-src/development/source_code] for instructions on getting the source.
Hardware support should be considered experimental. However, NUC's and Pixelbooks are known to work best. For details on hardware setup see: (Install Fuchsia on a Device)[https://fuchsia.dev/fuchsia-src/development/hardware/paving]
Once you have functional checkout you can (configure a build)[https://fuchsia.dev/fuchsia-src/development/build/fx#configure-a-build] targeting Workstation:
fx set workstation.<board> # For options run: `fx list-boards` fx build
See Fuchsia's (build and pave instructions)[https://fuchsia.dev/fuchsia-src/development/build/build_and_pave_quickstart] for detailed instructions.
Once built, standard Fuchsia workflows for paving, running code, and testing apply. See: (fx workflows)[https://fuchsia.dev/fuchsia-src/development/build/fx] for detailed instructions.