As I see there are always so many fights with MicroPython firmware size growth. That's why some ideas might not pass into codebase.
But how about adding such feature for build process that could define which parts to include into build and which not? For example some projects don't need framebuffer and graphics at all. Some do not need wifi. Some others do not need something else but need graphics. Some of them need just one framebuffer mode. It's like Linux kernel`s menuconfig (or command line options at least).
As a result fw build size may decrease even now for most of users.
IDEA: optional fw build
Re: IDEA: optional fw build
You mean something like this? https://github.com/micropython/micropyt ... nfigport.h
Re: IDEA: optional fw build
Yeah, but something more user(and/or script)-friendly. This headerfile could be modified as a result of option processingdeshipu wrote:You mean something like this? https://github.com/micropython/micropyt ... nfigport.h
Re: IDEA: optional fw build
You can already override those settings by passing options to the make command, I think.
Re: IDEA: optional fw build
There are some options that can be modified via make, but most of the options in mpconfigport.h need to come in through your board definition file.
Currently, the simplest way to have a customized build is to create a new board definition.
Currently, the simplest way to have a customized build is to create a new board definition.