Choose modules

--modules takes a comma-separated list:

./build.py --port rp2 --board RPI_PICO2 --modules displayif,jpegio,pygraphics,palettes,pdwidgets

A name is one of three things:

  • A short name from the modules table: displayif, pygraphics, omnipython.

  • A path, to a module of your own: a directory with a manifest.py, or a C module with its micropython.mk or micropython.cmake.

  • all: every module except the opt-in ones. picotts, tflite, vision and pdwidgets are opt-in (each has an OPT_IN file saying why), so name them to get them: --modules all,pdwidgets, --modules all,picotts, and for tflite and vision Use esp-vision’s modules.

A module never brings another, and nothing checks dependencies. If you name audioinstruments, audioeffects, tflite or vision, name ulab too, or use all.

Python packages from omnipython-lib

Our Python-only packages come from omnipython-lib: omnipython, palettes, pdwidgets, audioinstruments and audioeffects are modules whose manifest requires them from it. Any other package of it, such as a board config, can be named too.

The desktop board config

The desktop omnipython variants freeze a board config that imports displaydev. displaydev is frozen only when --modules names omnipython or all, so without one of them import board_config fails:

./build.py --port unix --variant omnipython --modules omnipython,displayif,pygraphics

A smaller image

all is large. On a small flash, name only what your project uses: Fit firmware on a small flash. audioinstruments and audioeffects can be cut down to the instruments and effects you use: Build with a few instruments and effects.