LGFX stuff and build size #362
Answered
by
tobozo
zensimilia
asked this question in
Q&A
-
|
How to do not compile all the LGFX stuff (fonts, LCD panels, platforms, touch, SPI etc.) if I need only CVBS and couple fonts? Does it (unused) extras affect build size? |
Beta Was this translation helpful? Give feedback.
Answered by
tobozo
Feb 27, 2023
Replies: 1 comment 3 replies
-
|
hello, thanks for your feedback 👍 When You can however reduce the build size by disabling autodetect (e.g don't use |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Thanx for answer! I don't use #pragma once
#include <LovyanGFX.hpp>
#define LGFX_BRIGHTNESS 128
#define LGFX_SATURATION 128
#define LGFX_USE_PSRAM 0
/**
* CVBS
*/
class LGFX : public lgfx::LGFX_Device
{
lgfx::Panel_CVBS _panel_instance;
public:
uint16_t _width;
uint16_t _height;
LGFX(uint16_t width = 240, uint16_t height = 160, uint8_t pin = DAC1) : _width(width), _height(height)
{
{
auto cfg = _panel_instance.config();
cfg.memory_width = width;
cfg.memory_height = height;
cfg.panel_width = width;
cfg.panel_height = height;
cfg.offset_x = 0;
cfg.offset_y = 0;
_panel_instance.config(cfg);
}
{
auto cfg = _panel_instance.config_detail();
cfg.signal_type = cfg.signal_type_t::NTSC; // NTSC | NTSC_J | PAL | PAL_M | PAL_N
cfg.pin_dac = pin; // 25 | 26
cfg.output_level = LGFX_BRIGHTNESS; // Brightness
cfg.chroma_level = LGFX_SATURATION; // Saturation
cfg.use_psram = 0;
if ((bool)LGFX_USE_PSRAM)
{
// 0=SRAM | 1=PSRAM/SRAM | 2=PSRAM
cfg.use_psram = 1;
// Reading PSRAM task priority
cfg.task_priority = 25;
// Core that executes the task of reading PSRAM
// in the background (APP_CPU_NUM | PRO_CPU_NUM)
cfg.task_pinned_core = PRO_CPU_NUM;
}
_panel_instance.config_detail(cfg);
}
setPanel(&_panel_instance);
};
LGFX(const LGFX &) = delete;
~LGFX() = default;
inline void drawColorTable()
{
this->clear();
for (int x = 0; x < this->width(); ++x)
{
int v = x * 256 / this->width();
this->fillRect(x, 0 * this->height() >> 3, 7, this->height() >> 3, this->color888(v, v, v));
this->fillRect(x, 1 * this->height() >> 3, 7, this->height() >> 3, this->color888(v, 0, 0));
this->fillRect(x, 2 * this->height() >> 3, 7, this->height() >> 3, this->color888(0, v, 0));
this->fillRect(x, 3 * this->height() >> 3, 7, this->height() >> 3, this->color888(0, 0, v));
}
};
};but build log always shows me compiling: touch, unused LCD panels etc. |
Beta Was this translation helpful? Give feedback.
-
then your binary already has the optimal size
it doesn't mean all those units are joined to your binary, if you look into the pio build dir and find the LovyanGFX folder you will see that there's ~56MB of units, which possibly can't fit in a firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification! |
Beta Was this translation helpful? Give feedback.
Answer selected by
zensimilia
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hello, thanks for your feedback 👍
When
LGFX_AUTODETECTis set, the v0/v1 units are compiled in every situation indeed, but they are cached so it only happens once, and only the platform components are attached to your binary.You can however reduce the build size by disabling autodetect (e.g don't use
#define LGFX_AUTODETECT) and setting up your own configuration (see user_settings example).