How does compiler handle library bloat in SMING framework?
Posted: Mon Apr 04, 2016 8:22 pmI am using the SMING framework on ESP8266. In the SMING framework, there are lots of libraries which get unused. For example, there are plenty of Adafruit-XXX libraries which are not relevant to non-Adafruit boards.
The SMING framework compiles into a pre-compiled library file that gets used up by the application sitting on top.
How does the compiler handle the unused libraries in the application compiled with the pre-compiled library SMING file? Do libraries consume RAM and flash even if unused? Should one remove these unused libraries to save RAM and code-space?
The SMING framework compiles into a pre-compiled library file that gets used up by the application sitting on top.
How does the compiler handle the unused libraries in the application compiled with the pre-compiled library SMING file? Do libraries consume RAM and flash even if unused? Should one remove these unused libraries to save RAM and code-space?