circuitpython/mpy-cross
Jeff Epler e7c74f273c
add translation to mpy-cross
2023-09-20 11:46:03 -05:00
..
mpy_cross mpy-cross/mpy_cross: Add docstrings to public methods. 2022-09-28 11:47:11 +10:00
Makefile add translation to mpy-cross 2023-09-20 11:46:03 -05:00
Makefile.fuzz Add license to some obvious files. 2020-07-06 19:16:25 +01:00
Makefile.m1 don't specify -sdk in Makefile.m1 for mpy-cross 2022-07-27 22:51:14 -04:00
Makefile.static Add license to some obvious files. 2020-07-06 19:16:25 +01:00
Makefile.static-aarch64 Build an aarch64 version of mpy-cross 2021-05-05 14:43:53 -05:00
Makefile.static-mingw fix name of windows mpy-cross executable 2021-10-15 08:53:58 -05:00
Makefile.static-raspbian remove trailing whitespace 2020-08-16 21:33:36 -05:00
README.md Merge tag 'v1.18' 2022-02-15 12:36:26 -06:00
fmode.c run code formatting script 2021-03-15 19:27:36 +05:30
fmode.h Add license to some obvious files. 2020-07-06 19:16:25 +01:00
gccollect.c Merge tag 'v1.17' into merge-1.17 2021-10-15 08:20:54 -05:00
main.c initial merge from v1.20.0; just satisifying conflicts 2023-09-19 11:10:12 -04:00
mpconfigport.h initial merge from v1.20.0; just satisifying conflicts 2023-09-19 11:10:12 -04:00
mphalport.h Merge MicroPython 1.10 into CircuitPython 2021-04-21 15:59:17 -07:00
mpy-cross.mk add translation to mpy-cross 2023-09-20 11:46:03 -05:00
mpy-cross.vcxproj all: Keep msvc build output in build/ directories. 2022-12-13 17:18:53 +11:00
qstrdefsport.h Add license to some obvious files. 2020-07-06 19:16:25 +01:00

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