The MicroPython project
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jim Mussared e4d90be680 mpy-cross/mpy_cross: Add docstrings to public methods. 1 week ago
mpy_cross mpy-cross/mpy_cross: Add docstrings to public methods. 1 week ago
Makefile mpy-cross/Makefile: Respect existing CFLAGS and LDFLAGS. 2 months ago all: Remove MICROPY_OPT_CACHE_MAP_LOOKUP_IN_BYTECODE. 1 year ago
gccollect.c all: Update to point to files in new shared/ directory. 1 year ago
main.c py/persistentcode: Introduce .mpy sub-version. 2 weeks ago
mpconfigport.h mpy-cross,unix: Include alloca.h for NetBSD. 1 month ago
mphalport.h mpy-cross: Make build independent of extmod directory. 4 years ago
mpy-cross.vcxproj windows: Unify project file headers. 7 months ago
qstrdefsport.h mpy-cross: Add new component, a cross compiler for MicroPython bytecode. 7 years ago

MicroPython cross compiler

This directory contains the MicroPython cross compiler, which runs under any Unix-like system and compiles .py scripts into .mpy files.

Build it as usual:

$ make

The compiler is called mpy-cross. Invoke it as:

$ ./mpy-cross

This will create a file foo.mpy which can then be copied to a place accessible by the target MicroPython runtime (eg onto a pyboard's filesystem), and then imported like any other Python module using import foo.

Different target runtimes may require a different format of the compiled bytecode, and such options can be passed to the cross compiler.

If the Python code contains @native or @viper annotations, then you must specify -march to match the target architecture.

Run ./mpy-cross -h to get a full list of options.

The optimisation level is 0 by default. Optimisation levels are detailed in