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.
 
 
 
 
 
 
Damien George aa0b8f340d mpy-cross/main: Use MICROPY_BANNER_NAME_AND_VERSION for --version. 3 months ago
..
mpy_cross mpy-cross: Add RISC-V RV32IMC support in MPY files. 5 months ago
Makefile extmod: Make extmod.mk self-contained. 2 years ago
README.md all: Remove MICROPY_OPT_CACHE_MAP_LOOKUP_IN_BYTECODE. 3 years ago
gccollect.c all: Update to point to files in new shared/ directory. 3 years ago
main.c mpy-cross/main: Use MICROPY_BANNER_NAME_AND_VERSION for --version. 3 months ago
mpconfigport.h py/emitndebug: Add native debug emitter. 5 months ago
mphalport.h mpy-cross: Make build independent of extmod directory. 6 years ago
mpy-cross.vcxproj all: Keep msvc build output in build/ directories. 2 years ago
qstrdefsport.h mpy-cross: Add new component, a cross compiler for MicroPython bytecode. 9 years ago

README.md

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 foo.py

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 https://docs.micropython.org/en/latest/library/micropython.html#micropython.opt_level