I built mpy-cross on but mpy files created with it cannot be used with the unix port's micropython executable because of a mismatching MICROPY_OPT_CACHE_MAP_LOOKUP_IN_BYTECODE definition. So I go ahead and put that to 0 in unix's mpconfigport.h. This results in:
Code: Select all
Creating build/frozen_mpy.c
CC build/frozen_mpy.c
build/frozen_mpy.c:7:2: error: #error "incompatible MICROPY_OPT_CACHE_MAP_LOOKUP_IN_BYTECODE"
#error "incompatible MICROPY_OPT_CACHE_MAP_LOOKUP_IN_BYTECODE"
This really feels like I'm doing something wrong or not as intended. Is there an easier way to do all this?
Also using 'python mpy-tool.py -d xxx.mpy' results in
Code: Select all
Traceback (most recent call last):
File "../tools/mpy-tool.py", line 593, in <module>
main()
File "../tools/mpy-tool.py", line 584, in main
dump_mpy(raw_codes)
File "../tools/mpy-tool.py", line 457, in dump_mpy
rc.dump()
File "../tools/mpy-tool.py", line 242, in dump
rc.freeze()
TypeError: freeze() takes exactly 2 arguments (1 given)
Sidenote: unix builds require seperate 'make axtls' and 'make' steps, but 'make clean' also cleans actls. That is confusing. Again, is this supposed to be used in another way maybe?