ESP8266 Community Forum

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?

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.

Can you put them in 2 directories? under the one.... if not I can do a crosstools also

Richard.

admin wrote:Can you put them in 2 directories? under the one.... if not I can do a crosstools also

Richard, I just requested transfer of both gcc and crosstool repos to esp8266.
The crosstool repo has gcc call0 ABI patches in it, so it's the only thing that's needed to build the toolchain.
gcc repo may be interesting to people who'd like to hack gcc more or to build it manually.