ppisa commented on issue #11907: URL: https://github.com/apache/nuttx/issues/11907#issuecomment-2732254373
> > I think that NuttX should be considered as a operating system and standard library base. > > That's great! Don't know how it relates to this conversation though 😄 . That means that if you export NuttX build for target then it is yet another C library for the RUST build, like GLibc, and you can use all RUST tools and conventions because you no longer dependent on NuttX build system. You only need to transform CFLAGS and Co. from nuttx-export/scripts/Make.defs to the RUST target defintion and specify that nuttx-export/libs/* and optionally some nuttx-export/startup/esp32c3_head.o should be included into target executable linking. That CFLAGS transformation to achieve ABI compatible RUST code build can be pain (even worse of embedded), because that is not 1:1 between GCC and LLVM (which again emphasizes my previously stated problem with RUST GCC frontend missing). See the FOSDEM talk Understanding ABI Compatibility between Compilers targeting RISC-V - ABI Extractor by Luis Silva https://fosdem.org/2025/events/attachments/fosdem-2025-4838-abi-extractor-understanding-abi-compatibility-between-compilers-targeting-risc-v/slides/237904/abi-extra_oLilQNM.pdf -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
