Daniel Eichhorn
My colleague Marcel recently developed a web based tool that lets you choose the modules which will be compiled into the NodeMCU build. This saves you the trouble to setup your own build server with tool chain and can save you a lot of space on the LUA heap, depending on how many modules you need to run your code: http://frightanic.com/nodemcu-custom-build/
 |
| Marcel’s NodeMCU Custom Build |
You select all the modules you need, enter your email address so you can be notified with the download link once the build has finished. The email will come with two links, one for the integer build and one for the build coming with floating point Math.
Curious on how much space on the heap this can save you I compared the current default build, downloaded from NodeMCU’s github page with a very minimalistic 7 module build (recommended default in the tool). The values come from a brand new NodeMCU Dev Kit V1.0 (the updated version) by sending =node.heap() directly after a clean start:
- Original Build: 20744 bytes
- Custom Build with 7 (default) modules: 26152 bytes
This means a difference of more than 5kb! This can be a welcome difference for a big project…
Seems like you mixed up the numbers, but I think everyone got it anyhow 🙂
heap(),the remain HEAP size in bytes
Is it possible to setup the toolchain in windows without a vm?
Found this by chance…Not sure I fully understand your question but there’s also a Docker image (from yours truly) with which you can build on Windows without the hassle of setting up the toolchain yourself.