d6d8722558
This makes it so that all a port needs to do is set the relevant variables and "include extmod.mk" and doesn't need to worry about adding anything to OBJ, CFLAGS, SRC_QSTR, etc. Make all extmod variables (src, flags, etc) private to extmod.mk. Also move common/shared, extmod-related fragments (e.g. wiznet, cyw43, bluetooth) into extmod.mk. Now that SRC_MOD, CFLAGS_MOD, CXXFLAGS_MOD are unused by both extmod.mk (and user-C-modules in a previous commit), remove all uses of them from port makefiles. Signed-off-by: Jim Mussared <jim.mussared@gmail.com> |
||
|---|---|---|
| .. | ||
| mpy_cross | ||
| Makefile | ||
| README.md | ||
| gccollect.c | ||
| main.c | ||
| mpconfigport.h | ||
| mphalport.h | ||
| mpy-cross.vcxproj | ||
| 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.
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