Discuss here different C compiler set ups, and compiling executables for the ESP8266

User avatar
By CHERTS
#9903
bkrajendra wrote:But let me tell you that 80% of this IT world do not trust any EXE unless it is digitally signed.
Hence it will be nice if you pack all of these tools in ZIP or RAR packages.
I hope there will not be any problem doing this, as you are not setting any system registry or environment variable in your installer. Even if its required you can provide sample BAT file or VBscript file or registry files.
You can even put entire content on github for better distribution and managment.
This will really grow the trust among developers and will also increase the popularity of your work.
I hope you understand my concerns.!


Starting with version DevKit 1.0.6 or higher (Espressif-ESP8266-DevKit-v1.0.x-x86.exe) my installer is signed by my digital signature, it was issued and certified Certum.

Image
User avatar
By CHERTS
#9917 A new version of my build Espressif DevKit for Windows v1.0.10
The list of changes to the first page

Update procedure:
1. Remove the old version.
2. Install the new version DevKit.
ATTENTION!!! When you delete the old version will be removed entire directory C:\Espressif
User avatar
By EspFan
#9965 Thanks! I installed this in a VM this weekend and everything works great. You are awesome!

Do you plan to update to the lastest Espressif SDK:
esp_iot_sdk_v0.9.5_15_01_23.zip

You can see the latest here:
https://github.com/esp8266/esp8266-wiki/tree/master/sdk
or here for official:
http://bbs.espressif.com/viewforum.php?f=5

This version shows some new features related to deep sleep so I am very interested to see how that works.
User avatar
By dpwhittaker
#9984
CHERTS wrote:A new version of my build Espressif DevKit for Windows v1.0.10


I had to reboot and run make from the command line to free up enough ram on my 1GB windows 8 tablet (make kept crashing and rebuilding the same folder over and over), but the NodeMCU build finally worked for me. I was having the linker error mentioned above on .irom0.text before, so it looks like this version resolves that issue.