xiaoxiang781216 commented on PR #3624: URL: https://github.com/apache/nuttx-apps/pull/3624#issuecomment-5101986818
> It seems that I am late to this party/iteration as the work is merged. > > @Acfboy has done sound work and as the Microwidows are fully optional component and the main work on NuttX drivers API related code is already integrated into mainline Microwidows, then merge can be base for next @Acfboy work and good opportunity for others to see the integration as preview. On the other hand I do not consider this as production ready/final version. > > @Acfboy has even prepared documentation and configs with examples configurations qemu-intel64:mw and sim:mw on related NuttX fork https://github.com/Acfboy/nuttx/commits/add-microwindows/ > > It would worth to be integrated through pull-request as well. But I would like to discuss some more options for example configurations. I would suggest to start the Microwidows demo through NSH to allow console access into running system for debugging, etc. But these are details which will be sorted out. > > As for the maim Microwindows integration, there worth to be done mone polishment to find reasonable way how to resolve warnings, solve [apache/nuttx#19527](https://github.com/apache/nuttx/issues/19527) (hope to find time to propose patch today). Then the test of more complex demos and applications based for example on X11 API should be tested. We will se where we find problems or some NuttX specific variants would be required... But as both Microwindows and NuttX use POSIX as main runtime model, it should be non-intrusive on both sides. > > I would be happy if components headers export for NuttX `make export` is solve in future which is useful not only for Microwidows but more general way. Thanks for the detailed summary and future plan. Do you have Nano X11 progress @ppisa ? -- 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]
