ead2554c78
Also move the construct earlier. This prevents the message ``` make: pitools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-gcc: Command not found ``` from occurring during the first build, since make was evaluating the line ``` mpy-cross.mk:COMPILER_TARGET := $(shell $(CC) -dumpmachine) ``` before $(CC) was created by the clone. Nothing bad seems to have come of this, but it's nice to fix it anyhow. (And interesting that it was lost among the spewed messages we're removing now) |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| fmode.c | ||
| fmode.h | ||
| gccollect.c | ||
| main.c | ||
| Makefile | ||
| Makefile.fuzz | ||
| Makefile.static | ||
| Makefile.static-mingw | ||
| Makefile.static-raspbian | ||
| mpconfigport.h | ||
| mphalport.h | ||
| mpy-cross.mk | ||
| qstrdefsport.h | ||
| 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.