mransom-campbell opened a new pull request #840: URL: https://github.com/apache/incubator-nuttx-apps/pull/840
I could use some feedback on this. It is still a WIP but it is taking longer than expected so I wanted to get this out there. ## Summary [Micropython](https://github.com/micropython/micropython) is a Python implementation for Microcontrollers. I think it is a perfect fit for NuttX. This PR adds NuttX as a Unix "Variant" under Micropython. This allows lots of features like files, sockets, etc.. to work without maintaining a separate Micropython port for NuttX. Notes: - Hardest part was integrating the build systems. Currently Micropython is built using the Micropython ports/unix Makefile during the "context" step. Building during the build step would be better but I couldn't get that to work. - I previously manually specified all the .c files but that broke as soon as I updated Micropython. I am far from a Make expert so if anyone has a better solution let me know. - Currently clones my fork of Micropython (https://github.com/mransom-campbell/micropython/tree/nuttx). I will upstream those changes once I do some cleanup. - Would it be better to download the latest Micropython release and apply patches like the Duktape NuttX support? TODO: - [x] Add NuttX support to Micropython Unix port. - [x] Create Makefile and KConfig for NuttX Apps. - [ ] Fix warnings when sockets/ussl are enabled (NuttX builds will -Werror) - [ ] Fix Micropython stack check size. - [ ] Add Micropython default Heap size as configuration option. - [ ] Run Micropython test suite ## Impact Application.mk: changed OBJS to be += so Applications can add their own object files manually. ## Testing I have tried a few things on a stm32 board and Renesas RX board, everything seems to work. The full Micropython test suite should be run before this PR is merged. -- 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]
