circuitpython/mpy-cross
Jeff Epler 74bf17bb0d Makefiles: add targets to build unix port, mpy-cross for fuzzing
This assumes you have properly install afl-fuzz with afl-clang-fast.
Tested with AFLplusplus 2.60c-75-g2c6847b.
2020-03-01 11:48:33 -06:00
..
.gitignore Makefiles: add targets to build unix port, mpy-cross for fuzzing 2020-03-01 11:48:33 -06:00
Makefile mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06:00
Makefile.fuzz Makefiles: add targets to build unix port, mpy-cross for fuzzing 2020-03-01 11:48:33 -06:00
Makefile.static mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06:00
Makefile.static-mingw mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06:00
Makefile.static-raspbian Add a makefile to cross-compile for raspbian 2020-01-25 15:32:52 -06:00
README.md mpy-cross: Add new component, a cross compiler for MicroPython bytecode. 2016-02-25 10:12:21 +00:00
fmode.c mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06:00
fmode.h mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06: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 Define serial_write, it was undefined in the Windows mpy-cross build 2020-01-25 15:09:49 -06:00
mpconfigport.h handle errno defns for mingw and use correct executable name 2018-07-10 22:29:36 -04:00
mphalport.h mpy-cross: Add new component, a cross compiler for MicroPython bytecode. 2016-02-25 10:12:21 +00:00
mpy-cross.mk mpy-cross: Make it easier to build mpy-cross static targets 2020-01-25 14:04:11 -06: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.