On Sun, Oct 17, 2021 at 1:06 AM Abdelatif Guettouche wrote: > There isn't really a big difference between IDF's toolchain and the one > from Sifive, this is why we didn't add both. > Are you having issues running the one from SiFive?
I know SiFive, I am following them directly at RISC-V lists, I am (individual) member of the organization :-) I would prefer to use system provided packages in the first place, then ESP-IDF second, then anything external that needs manual intervention. The goal is to create automation bootstrap.sh in the top level of my project source code so it sets up whole build environment and produce the firmware for clients with only one script. Using ESP-IDF toolchain gives me all tools necessary for that on various platforms and because these are the same tools different compiler problems are reduced to almost zero. I made this with MBED and Zephyr, it works quite well, I also want to have something like this with NuttX :-) > The CROSSDEV variable will just have the name of the toolchain. If we want > to add another toolchain we add another ifeq in > riscv/rv32im/Toolchains.defs. Thank you :-) I can see there are many variants of the RV. That would imply changing many files. Can we put that in some sort top level Toolchains.defs and then include that in machine variants configuration? Will try that and provide patches / pr :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
