7/29/2023 0 Comments Espressif esp32 fritzingAs one of the replies said, I was talking mostly about the IoT space, but I think it's true for the non-IoT laptop/server space as well. The one annoyance in all of the embedded toolkits when trying to use non-C/C++ languages is always CMake companies build component systems and such on top of it which a naive C compiler usage can’t really leverage, which means you end up rebuilding the whole build toolchain again.Įasier to just stick within CMake and use Nim’s C output instead, at least for now (until I get some time to write a nimscript parser for a subset of ESP-IDF’s CMake file format…) That said, if I was on the C3 or any of the RISC-V chips I’d look at using the C toolchain directly: you can easily have “nim c main.nim” call out to a specific C compiler with your specific build and linker flags! With #line macros injected into the compiled C output source files, JTAG debugging and other tools just work, which is quite nice. So the S3 is actually a Xtensa LX7 processor rather than a RISC-V one, but the process is the same: “-compileOnly” to output C sources from Nim, and point CMake to that nimcache output folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |