ppisa commented on issue #11907: URL: https://github.com/apache/nuttx/issues/11907#issuecomment-2731993935
@nakajimayoshi I think that NuttX should be considered as a operating system and standard library base. In this case build by make/Cmake etc. is right way. It should be configured and provide runtime environment. It allows even load of ELF binaries at runtime. They can be build out of NuttX build when NuttX export provides standard C library, syscalls base headerfiles and low level RUST adaptation. So you can use all bells and whistlers of the RUST best practices build system exactly same way as on the GNU/Linux. If you do not want to build runtime loadable binary then you include NuttX kernel library (.a files) in the final link phase and you again work exactly same way as on the GNU/Linux when you link static GLibc. There are some thinks to resolve: - for NuttX export on RISC-V and may it be others there is unresolved issue https://github.com/apache/nuttx/issues/6082 - I consider dependence on RUST in Linux kernel and other projects at significant threat to long term open source sustainability until there is full featured RUST compiler based on fully GNU or other copyleft licensed compiler (LLVM has private commercial branches, i.e. Apple which can prevail if companies in control decide stop the community version funding and community version is used (as I know) only for cherry-picking but kept on M1 and other far behind closed one). So R.M.S. 1984 experience leading to GNU project start matters there. There are too many PR proclamations from the RUST proponent, but when I have looked for company which would fund my student which step in to fill this RUST fundamental gap (https://dspace.cvut.cz/bitstream/handle/10467/113390/F3-DP-2024-Dupak-Jakub-thesis.pdf) then there has been found nobody willing to fund the GCC RUST fronted development continuation (the borrow checker integration in this case)... So I suggest to be very careful about depend ency on RUST and its build ecosystem for now. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
