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

User avatar
By CHERTS
#16028
mbruck wrote:1. Please would you explain me is your devkit support expressif SDK's ? I mean recently it is announced new version ESP8266 SDK (esp_iot_sdk_v1.0.1_b2_15_04_10) on esperssif web page.


The DevKit v2.0.3 already included official Espressif SDK v1.0.1
User avatar
By Markus Gritsch
#16035 @CHERTS: I noticed, that in your included examples\nodemcu-firmware project, you have commented out #define LUA_USE_BUILTIN_MATH in user_modules.h.

I assume, it is because the NodeMCU build fails otherwise, as described here:
viewtopic.php?f=23&t=2030

Do you know what to change to have your toolchain produce the same binaries as the toolchain available for Linux/Ubuntu? Do you intend to fix this?
User avatar
By cherowley
#16099 I can't get step 5 to work .. it shows lots of errors saying (small exceprt):

install: automake-1.11.1-1-msys-1.0.13-lic.tar.lzma
mingw-get: *** ERROR *** package automake-1.11.1-1-msys-1.0.13-lic.tar.lzma is a
lready installed
install: mktemp-1.6-2-msys-1.0.13-bin.tar.lzma
mingw-get: *** ERROR *** package mktemp-1.6-2-msys-1.0.13-bin.tar.lzma is alread
y installed

Will this matter? :)
User avatar
By CHERTS
#16367
Markus Gritsch wrote:Do you know what to change to have your toolchain produce the same binaries as the toolchain available for Linux/Ubuntu? Do you intend to fix this?


The GCC compiler in DevKit is the same as for Linux, it is based on the project https://github.com/jcmvbkbc/gcc-xtensa.git