Kisszalimo commented on issue #3066:
URL: https://github.com/apache/mynewt-core/issues/3066#issuecomment-1722585164
@kasjer thank you for your response. I added a new repo including the PR you
mentioned to my project. On the first try, the problem was not solved:
```
Error: /usr/lib/gcc/arm-none-eabi/10.3.1/../../../arm-none-eabi/bin/ld:
/home/(...)/apache-mynewt-newt-bin-linux-1.11.0/limon_v1/bin/targets/limon_v1/app/apps/blinky/blinky.elf
section `.bss' will not fit in region `RAM'
/usr/lib/gcc/arm-none-eabi/10.3.1/../../../arm-none-eabi/bin/ld: region RAM
overflowed with stack
/usr/lib/gcc/arm-none-eabi/10.3.1/../../../arm-none-eabi/bin/ld: region
`RAM' overflowed by 248 bytes
```
However, the amount of overflowed bytes has decreased a lot. So on the
second try, I modified my target `syscfg.yml` file according to your advice,
and then the project built successfully.
Before Mynewt supported LVGL, there was [an unofficial
port](https://github.com/lupyuen/pinetime_lvgl_mynewt/tree/master) to Mynewt.
The main difference is the version of LVGL: the unofficial port uses V7, while
Mynewt port uses V8. I thought it would be interesting to compare these two
ports, so I ran a [benchmark
demo](https://github.com/lvgl/lvgl/tree/master/demos/benchmark) to test both
ports. Unfortunatelly it seems the older port cannot measure the performance
properly (or I did something wrong), because it shows very high results (e.g.
weighted FPS: 9000), which does not make any sense.
So finally I created two very simple scrolling-label demos using both ports.
The functionality and included libraries (except ports) are the same. Strangely
the size of generated image files differs significantly:
**Image size using Mynewt port:** 219KB
**Image size using older port:** 138KB
I am wondering what causes this big difference and how can we reduce it.
Probably the new version of LVGL requires more space... or newt wants to
compile "too much thing" into the image?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
