-
• #2
I executed: scripts/create_espruino_image_1v3.sh and I was able to successfully compile :-)
I read in: https://github.com/espruino/Espruino#building-for-stm32-boards-incl-espruino-board that the user can remove features such as graphics. Are there any other features that I can remove to further shrink the binary down? I plan to attempt to custom compile a binary with AES encryption features (no promises that I will succeed).
UPDATE
I realize that I should of executed create_pico_image_1v3.sh instead of espruino 00ps... -
• #3
Ahh - the thing you might have been missing is
RELEASE=1
on the command-line. I'll update the docs (they mention it for Linux, but not when building using a VM). Building withoutRELEASE=1
compiles in debug checks, which take space and slow Espruino down, but which also make sure nothing is going horribly wrong with any changes that might have been made :)If you take a look in
Makefile
underifdef PICO_1V3
you'll see lines titledUSE_xxx
that you can remove - however the Pico itself has almost certainly got enough free space without doing that - it's only the original Espruino board that's getting a bit tight now.
I'm following this guide with a minor change: https://github.com/espruino/Espruino#building-under-windowsmacos-with-a-vm
I am using the 64 bit version instead of the 32 bit version
Error: