Skip to content

Docs: Investigate the fork's desktop paths on macOS (#191) - #243

Merged
b-re-w merged 1 commit into
developfrom
feat/fork-desktop-paths-doc
Oct 17, 2026
Merged

b-re-w merged 1 commit into
developfrom
feat/fork-desktop-paths-doc

Conversation

@b-re-w

@b-re-w b-re-w commented Oct 17, 2026

Copy link
Copy Markdown
Member

Closes #242

Documentation: docs/investigations/fork-desktop-paths-macos.md. Read-only, from the fork's origin/extended branches, ~/.m2 and develop; nothing was built.

Key findings:

  • The fork's measured GraalVM result is Compose in an AWT window inside a native image. The AWT-free GraalVM window opens and presents, but no published piece draws Compose into it: graalvm-macos has no WindowSurface, and scene is not published.
  • The upcall table carries over to a native image unchanged (its FFM metadata ships in the jar). PYTHONHOME staging does not: nothing stages a prefix beside an executable.
  • The Kotlin/Native path needs a new macosArm64 interpreter target and a klib walker closer to the jar walker.
  • First milestone: the notebook E2E in a macOS native image. It draws offscreen, so no window is needed.
  • Six requests for the fork, listed in the document for the darkpyonix lead.

What PMP needs to build the fork's GraalVM native-image and Kotlin/Native
paths from its mavenLocal artefacts, whether the upcall table and
PYTHONHOME staging carry over, the first milestone (the notebook E2E in
a macOS native image, offscreen, so no window is needed), and the list
of requests for the fork.

Closes #242
@b-re-w
b-re-w merged commit c20546c into develop Oct 17, 2026
@b-re-w
b-re-w deleted the feat/fork-desktop-paths-doc branch October 17, 2026 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant