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

User avatar
By jcmvbkbc
Squonk wrote:However, It may be interesting to automatically check for the prerequisites to avoid sibylline error messages while compiling.
Another suggestion would be to have all the required sources into a single git repository (including binutils, gdb and newlib), so you just have to clone the repository and compile. This will enable sharing future updates by just pulling them in one single place.

Yet another option might be updating crosstool-NG and using it. I'm looking at it right now.
When it works all we need to build a toolchain is a config file and an overlay file. We can put them to lx106-specific branch of crosstool-NG, the rest it will take care of.
User avatar
By RichardS
#1093 Log onto http://www.github.com and get a personal account, then PM me your username and I will add you as a collaborator....

User avatar
By Squonk
#1094 We can do both...

Use Github first to share the tools and make fast changes until it becomes stable, maybe to turn it into a clean crosstool-ng update?
User avatar
By jcmvbkbc
jcmvbkbc wrote:Yet another option might be updating crosstool-NG and using it.

Ok, done that: https://github.com/jcmvbkbc/crosstool-NG/commits/lx106
The build procedure is the following:

Clone it:
$ git clone -b lx106 git://github.com/jcmvbkbc/crosstool-NG.git
$ cd crosstool-NG

Build crosstool-NG:
$ ./bootstrap && ./configure --prefix=`pwd` && make && make install

Configure it for lx106:
$ ./ct-ng xtensa-lx106-elf

And build the toolchain:
$ ./ct-ng build

Toolchain binaries will be under builds/xtensa-lx106-elf/bin

Not sure what to put to https://github.com/esp8266/gcc-compiler. I'd rather put both crosstool and gcc to separate repos.