Skip to content

graphics/microwindows: add Nano-X client/server support and examples for NuttX - #3689

Draft
Acfboy wants to merge 8 commits into
apache:masterfrom
Acfboy:add-microwindows
Draft

graphics/microwindows: add Nano-X client/server support and examples for NuttX#3689
Acfboy wants to merge 8 commits into
apache:masterfrom
Acfboy:add-microwindows

Conversation

@Acfboy

@Acfboy Acfboy commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR ports the Nano-X windowing system from Microwindows to NuttX so that X11-style client/server applications can run in a flat build. It contains three logical parts:

  1. graphics/microwindows: build the Nano-X client library and server from the bundled Microwindows tree, with two new Kconfig options:
    • MICROWINDOWS_NANOX: build the Nano-X client library and server.
    • MICROWINDOWS_NANOX_NANOWM: optionally link the Microwindows window manager into the server so the server task draws and decorates windows itself.
  2. examples/nanoxcalc: port of the nxcalc demo. It connects to the running Nano-X server and shows a calculator keypad.
  3. examples/nanoxterm: port of the nxterm demo. It is a terminal emulator that opens a pseudo terminal, forks, and runs an NSH instance (nsh_consolemain) in the child instead of exec'ing /bin/sh, since flat builds have no filesystem binaries. It starts the Nano-X server as a separate task before connecting, so it can be used as the init entry point: booting sim:nanox opens the nxterm window directly, and typing nanoxcalc in it opens the calculator.

Note

There are still some remaining issues, for example, have some problem when running on qemu, so this is just a draft PR. When it is fully ready, I will add the documentation and open it up for review.

Acfboy added 4 commits July 30, 2026 00:04
Without this Make variable, Objects.rules does not add font_fnt.o
to the build, causing undefined reference to fnt_createfont at link time.

Signed-off-by: Acfboy <AcfboyU@outlook.com>
…support for NuttX

Build the Nano-X client library, server and (optional) built-in window manager
from the bundled Microwindows tree

Signed-off-by: Acfboy <AcfboyU@outlook.com>
* Port the nxcalc demo from Microwindows
* Connects to the Nano-X server started by examples/nanoxterm
* Requires CONFIG_LIBC_FLOATINGPOINT for the result formatting

Signed-off-by: Acfboy <AcfboyU@outlook.com>
* Port the nxterm demo from Microwindows
* Starts the Nano-X server as a separate task before connecting
* Runs an NSH shell instance on a pseudo terminal in the forked child
  instead of exec /bin/sh (no filesystem binaries in flat builds)

Signed-off-by: Acfboy <AcfboyU@outlook.com>
@cederom

cederom commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Thank you @Acfboy :-)

For sure we need a documentation for that part :-) I just did a rewrite of components / graphics / nx, so other gfx components are in one place, like framebuffer, and maybe nano-x, will push in a free moment this week :-)

Acfboy and others added 4 commits August 12, 2026 08:47
* Port the nxterm demo from Microwindows
* Port the nxcalc demo from Microwindows
* Starts the Nano-X server as a separate task before connecting
* Runs an NSH shell instance on a pseudo terminal in the forked child
  instead of exec /bin/sh (no filesystem binaries in flat builds)

Assisted-by: OpenCode:DeepSeek-V4-Flash
Signed-off-by: Acfboy <AcfboyU@outlook.com>
* Introduce EXPORTED_INCLUDES in apps/Make.defs; every entry is
  prefixed with INCDIR_PREFIX and added to CFLAGS/CXXFLAGS so it
  takes effect in the in-tree build as well
* The export target in apps/Makefile copies the content of the listed
  directories into the include directory of the export package, so
  out-of-tree applications built from the package can still find the
  public headers
* graphics/microwindows registers microwindows/src/include through
  this mechanism in its Make.defs

Assisted-by: OpenCode:DeepSeek-V4-Flash
Signed-off-by: Acfboy <AcfboyU@outlook.com>
…h the server

* Add CONFIG_MICROWINDOWS_NANOX_NONETWORK which builds the Nano-X
  client library and server in the linked-in (NONETWORK) mode, so
  client applications are linked directly with the server and run in
  the same task, requiring no network stack or socket at all
* Reorganize the source lists: the drawing sources (nxdraw, nxutil,
  nxtransform, nxpaintnc) are shared by both modes, while the server
  is built from srvnet.c in the network mode and srvnonet.c in the
  NONETWORK mode
* Use MULTITHREAD_SERVER in the network mode so that several client
  tasks can run at the same time in the flat build
* Let the examples/nanoxterm start the server task only in the
  network mode (NONETWORK applications run the server inside main)

Assisted-by: OpenCode:DeepSeek-V4-Flash
Signed-off-by: Acfboy <AcfboyU@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants