Rather than running the runloop forever, have the API expose an incremental runloop. This allows clients to do other processing if they need it.
This allows for removing the odd construction of having knowledge of GTK event handling built into the library even though nothing in the library uses it; instead runner applications that use GTK plugins (such as FDE's testbed) can do that processing at the application level instead.
Almost all of the python build files in the flutter project work if
`python` is `python2` or `python3`. This is the only area where print is
incorrectly used (for `python3`).
Related issue: https://fuchsia-review.googlesource.com/c/fuchsia/+/272925
Simplifies the build and runtime requirements for the Linux shell.
Since the engine does GL extension lookup manually anway, an extension
loader library isn't necessary.
Installs the dependencies necessary to build the Linux desktop shell.
Similar to the existing install-build-deps.sh and
install-build-deps-android.sh but specifically for the desktop shell
requirements.
A flutter_app target might be declared in a build file alongside some host tool.
The intent of the assertion seemed to be restricting the use of the template to the Fuchsia codebase.