lvgl-rs/README.md

58 lines
2.1 KiB
Markdown
Raw Normal View History

2020-04-12 07:58:01 +00:00
<h1 align="center"> LittlevGL - Open-source Embedded GUI Library in Rust</h1>
2020-05-30 07:37:40 +00:00
![Original LittlevGL demo image](lv_demo.png)
2020-04-12 07:58:01 +00:00
<p align="center">
LittlevGL provides everything you need to create a Graphical User Interface (GUI) on embedded systems with easy-to-use graphical elements, beautiful visual effects and low memory footprint.
2020-04-12 08:03:02 +00:00
</p>
<p align="center">
2020-04-12 08:10:04 +00:00
LittlevGL is compatible with <samp>#![no_std]</samp> environments by default.
2020-04-12 07:58:01 +00:00
</p>
<h4 align="center">
2020-05-30 07:37:40 +00:00
<a href="https://lvgl.io/">Official LittlevGL Website </a> &middot;
2020-04-12 10:32:18 +00:00
<a href="https://github.com/littlevgl/lvgl">C library repository</a> &middot;
2020-05-30 07:37:40 +00:00
<a href="https://lvgl.io/demos">Live demo</a>
2020-04-12 07:58:01 +00:00
</h4>
---
2020-04-12 10:34:03 +00:00
![Rust bindings usage demo code.](demo.png)
2020-04-12 18:37:26 +00:00
## Usage
Edit your `Cargo.toml` file dependencies with:
```
$ cargo add lvgl
```
The build requires the environment variable bellow to be set:
- `DEP_LV_CONFIG_PATH`: Path to the directory containing the `lv_conf.h` header file used for configuration of LittlevGL library.
We recommend the `lv_conf.h` file to be in your project's root directory. If so, the command to build your project would be:
```shell script
$ DEP_LV_CONFIG_PATH=`pwd` cargo build
```
### Building for embedded environments
We make use of `bindgen` for generating the bindings to LittlevGL at build time. There is a problem in cargo when building
for `no_std`, so we need to use a workaround to build "lvgl-rs". The mainstrem issue in cargo is being tracked at
[rust-lang/cargo#7915](https://github.com/rust-lang/cargo/issues/7915).
```shell
$ DEP_LV_CONFIG_PATH=`pwd` cargo build -Zfeatures=build_dep
```
#### Requirements / Limitations
LittlevGL C libary do allocate memory dynamically and we need to allocate memory on the heap in the Rust side as well
([`Box`](https://doc.rust-lang.org/beta/alloc/boxed/struct.Box.html)).
That is required, so we can safely provide Rust pointers through FFI. For that reason, we do require
[`alloc`](https://doc.rust-lang.org/alloc/) module to be available.
## Running the demo
[This project contains an example that can run in a desktop simulator.](./examples/demo)