History

Alexander Steffen 55f33240f3 all: Use the name MicroPython consistently in comments There were several different spellings of MicroPython present in comments, when there should be only one.		2017-07-31 18:35:40 +10:00
..
.gitignore	mpy-cross: Add new component, a cross compiler for MicroPython bytecode.	2016-02-25 10:12:21 +00:00
Makefile	all: Use the name MicroPython consistently in comments	2017-07-31 18:35:40 +10:00
README.md	mpy-cross: Add new component, a cross compiler for MicroPython bytecode.	2016-02-25 10:12:21 +00:00
gccollect.c	py: Add MP_STATE_THREAD to hold state specific to a given thread.	2016-06-28 11:09:31 +01:00
main.c	all: Don't include system errno.h when it's not needed.	2017-07-24 18:43:14 +10:00
mpconfigport.h	mpy-cross, unix, windows, stmhal: Enable return-if-else optimisation.	2017-04-22 15:12:48 +10:00
mphalport.h	mpy-cross: Add new component, a cross compiler for MicroPython bytecode.	2016-02-25 10:12:21 +00:00
qstrdefsport.h	mpy-cross: Add new component, a cross compiler for MicroPython bytecode.	2016-02-25 10:12:21 +00: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. For example, the unix port of MicroPython requires the following:

$ ./mpy-cross -mcache-lookup-bc foo.py

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