As the title says... Chat on...

User avatar
By iHaveESP
#8277 NodeMCU features, have expanded greatly and many thanks to those who have contributed!!!

It seems to me that 0.9.5 sdk is currently being used. To date, I haven't set up my own firmware compiling environment. Is it now recommended, that we set this up and users compile their own firmware to enable/disable features(LUA_NUMBER_INTEGRAL in user_config.h)? I have relied on pre-compiled bins.

I think this is a worthy discussion for the future of prebuilds.

Depending upon the use case and the desire to maximize heap, unless a user can compile their own firmware, the continuation of adding new features breaks current code and further reduces needed heap for other things.

Would it be possible to do pre-builds based on what's enabled or disabled in them? floats, mqtt, node.readvdd33(), etc...? I can't test how taxing these are, but I think it's a good option.

-Thanks!
User avatar
By sej7278
#8311 i think if you want custom features enabled/disabled you'd have to do it yourself, compiling every type of prebuild bin would not be maintainable.

luckily its quite simple these days:

Code: Select allgit clone https://github.com/pfalcon/esp-open-sdk.git
cd esp-open-sdk
make


add esp-open-sdk/xtensa-lx106-elf/bin to your $PATH

Code: Select allcd ..
git clone https://github.com/nodemcu/nodemcu-firmware.git
cd nodemcu-firmware
make && make flash


so you'd make your changes before that last make.
User avatar
By iHaveESP
#8426 ...many thanks, that was easy! pfalcon did a great job on the sdk install program!

After installing all the dependencies listed herehttps://github.com/esp8266/esp8266-wiki/wiki/Toolchain and making the path stick in .bashrc.

...all was good. I now have my heap back, can customize and try other things as well :D

Cheers!