ppisa commented on code in PR #3624:
URL: https://github.com/apache/nuttx-apps/pull/3624#discussion_r3655141101
##########
examples/microwindows/mwdemo_main.c:
##########
@@ -0,0 +1,32 @@
+/****************************************************************************
+ * apps/examples/microwindows/mwdemo_main.c
+ *
+ * NuttX entry point for mwdemo (Microwindows Win32 API demo)
+ ****************************************************************************/
+
+/****************************************************************************
+ * Included Files
+ ****************************************************************************/
+
+#include <nuttx/config.h>
+#include "windows.h"
Review Comment:
The one of Microwindows APIs provides some basic compatibility with Windows
GDI API and it is then possible to port applications from Windows there. But it
is possible to use GDI even fully without this partial compatibility layer same
as X11 APIs etc. So this example shows how this compatibility can be used.
There is attempt to show how such minimal demo can be added to NuttX. On the
other hand, demos can be build directly from Microwindows sources so we can
left this only there. Windows API substitution file is provided by
`microwindows/src/include/windows.h`. It would worth to think about setup where
microwindows header files are provided in some subdirectory to `include` that
application can decide if it wants or does not want access to these...
So this is for discussion. But large part of Microwindows value is providing
APIs which allows to port applications programmed against different massively
used graphic full featured stacks to embedded systems if reasobale subset of
APIs is used.
--
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]
