Post
by mcL » Thu Jun 25, 2020 8:21 pm
Ok, figured it out, so I will answer my own question in case other run into this (others have as indicated by issue #5320 and elsewhere). I don't know if this is the blessed way to resolve this (please advise if you know a better procedure).
Problem:
* Manifest files are exclusive OR: only one or the other is used for the build. There is the standard one in ..boards/. If one wants a custom (freeze some of your scripts) you'll probably want to make a your own manifest.py in your project directory (so it can be tracked via git/etc.) and put your scripts in there.
* If you use the FROZEN_MANIFEST directive to use that, the standard one won't be used; only your project one is used. This means (I guess) that the standard ones, which you want/need, will be excluded.
* This is confusing as ../frozen_mpy still shows the other/older/orginal .mpy files. I think it's fair for the user to assume that those .mpy files would all be used in the make. Apparently they aren't.
Solution: (please advise if you of a better way, maybe with an 'include'. Just happy to get it working I don't want to break it again!)
* Copy/paste contents of ../boards/manifest.py and and append to your projects manifest.py
* re-make (in my case) with BOARD=GENERIC_1M FROZEN_MANIFEST=<your_project_dir>/manifest.py. erase, flash, smile, crack a beer.