Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/chinmaygarde/flutter_from_scratch
A minimal Flutter Embedder from Scratch.
https://github.com/chinmaygarde/flutter_from_scratch
clang cpp flutter gn raspberry-pi
Last synced: 12 days ago
JSON representation
A minimal Flutter Embedder from Scratch.
- Host: GitHub
- URL: https://github.com/chinmaygarde/flutter_from_scratch
- Owner: chinmaygarde
- Created: 2018-11-27T23:32:23.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2022-05-20T02:13:12.000Z (over 2 years ago)
- Last Synced: 2024-10-18T20:44:08.353Z (25 days ago)
- Topics: clang, cpp, flutter, gn, raspberry-pi
- Language: C++
- Size: 11.7 KB
- Stars: 158
- Watchers: 15
- Forks: 26
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Notes:
------
* This is the companion repository for the `Flutter on Raspberry Pi (mostly) from Scratch` [article](https://medium.com/flutter/flutter-on-raspberry-pi-mostly-from-scratch-2824c5e7dcb1).
* This repository is only meant to showcase what a minimal embedder might look like. It is not production ready (and never will be)!
* Though this repository is based off of the [Raspberry Pi Cross Compilation SDK and GN Sysroot](https://github.com/chinmaygarde/raspberrypi_cross_compilation_sdk) repository. You dont have to use this toolchain or GN.Flutter on Raspberry Pi
=======================Flutter Embedder for Pi using Broadcom APIs directly.
Prerequisites
-------------* The `libflutter_engine.so`, `icudtl.dat` and `flutter_embedder.h` files for the Raspberry Pi placed in the `out/` directory.
Usage for Raspberry Pi
----------------------* Download the prepared toolchain, sysroot and related tools to the `out` directory `./tools/setup_sdk.sh`.
* This takes a while and downloads upto 1 GB of data from cloud storage.
* Prepare the build output directory `out` with paths to your toolchain using `./tools/setup_gn.sh`.
* Build using `ninja -C out` on your host.
* Hack and repeat.
* Push your executable to the Raspberry Pi and run.
* You should probably mount the `out` directory to the remote Raspberry Pi using SSHFS. That way, the build artifacts automatically end up getting pushed to the Pi.