- Sun May 10, 2015 8:25 am
#17079
If you regularly want to build your custom NodeMCU firmware I suggest you give http://frightanic.com/nodemcu-custom-build/ a spin. You select the branch to build from, select the user modules to include (to reduce firmware size) and my service will build a firmware just for you.
- Sun May 10, 2015 12:37 pm
#17102
Great idea. Trying it now.
I would suggest putting as much information as possible on the site.
I would suggest putting as much information as possible on the site.
- Sun May 10, 2015 1:52 pm
#17109
Submitted my request. Received and email that it was started. 2 minutes later another email was received with 2 links for float and integer binaries.
Excellent work.
I have two suggestions. Include more information on the web site and include what was selected for compile in the completed email.
Excellent work.
I have two suggestions. Include more information on the web site and include what was selected for compile in the completed email.
- Sun May 10, 2015 2:48 pm
#17112
Thanks for your valuable feedback.
Ok, like what? What were you missing?
Yes, definitely. I realized that many users commission several builds in quick succession and then won't have much clue as to what a particular binary contains when they get several success emails in quick succession.
For a moment I thought about letting users give their builds meaningful names but I believe just stating branch and selected modules in the success email is enough. Furthermore, the firmware filename should be something like '<branch>-<number-of-modules>-modules-[integer|float]-<hash>.bin' or so.
Include more information on the web site
Ok, like what? What were you missing?
include what was selected for compile in the completed email
Yes, definitely. I realized that many users commission several builds in quick succession and then won't have much clue as to what a particular binary contains when they get several success emails in quick succession.
For a moment I thought about letting users give their builds meaningful names but I believe just stating branch and selected modules in the success email is enough. Furthermore, the firmware filename should be something like '<branch>-<number-of-modules>-modules-[integer|float]-<hash>.bin' or so.
