| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Freezing mpy files using mpy-tool.py now works again.
|
| |
|
|
|
|
|
|
|
|
| |
Now frozen modules is treated just as a kind of VFS, and all operations
performed on it correspond to operations on normal filesystem. This allows
to support packages properly, and potentially also data files.
This change also have changes to rework frozen bytecode modules support to
use the same framework, but it's not finished (and actually may not work,
as older adhox handling of any type of frozen modules is removed).
|
| |
|
|
|
| |
This allows for better error messages, since the name of the file (sans
.py) can now be printed when an exception occurs within a frozen script.
|
| |
|
|
|
|
|
| |
The config variable MICROPY_MODULE_FROZEN is now made of two separate
parts: MICROPY_MODULE_FROZEN_STR and MICROPY_MODULE_FROZEN_MPY. This
allows to have none, either or both of frozen strings and frozen mpy
files (aka frozen bytecode).
|
| | |
|
| | |
|
| |
|
|
| |
To allow simple zero-terminated lexers.
|
| | |
|
|
|
Only modules (not packages) supported now. Source modules can be converted
to frozen module structures using tools/make-frozen.py script.
|
