Skip to content

Commit 40feb36

Browse files
committed
docs(eui-neo): record the macOS/Windows CI evidence for the new members
PR #139 run 30502516910: all three workspace legs selected the same six eui-neo members and passed (linux 12m26s, macos 6m15s, windows 7m50s). The app-main assertion is self-proving and worth spelling out: the test TU defines no main(), so the binary can only run if glfw_app_main.o supplied one. Its 'linked, main() supplied by the package' line appearing on the windows and macos legs is proof that TU compiled and linked there for the first time — which is what exercises the -D_WIN32_WINNT=0x0A00 and -lkernel32 additions.
1 parent 963e5e1 commit 40feb36

1 file changed

Lines changed: 26 additions & 4 deletions

File tree

.agents/docs/2026-07-30-eui-neo-window-and-app-main-members.md

Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -183,10 +183,32 @@ eui-neo-markdown (existing) ok
183183
`check_cross_package_refs.lua` all pass on the touched descriptor. The descriptor
184184
change is comment-only.
185185
186-
**macOS and Windows are CI-verified only.** There is no runner for either here, so
187-
the build+link half of both members on those platforms is asserted by the
188-
`workspace (macos)` / `workspace (windows)` legs, not locally. Two things are new
189-
there and worth watching on the first run:
186+
**macOS and Windows are CI-verified, not locally verified** — there is no runner for
187+
either here. PR #139, run 30502516910: all three `workspace` legs selected the same
188+
six members and passed.
189+
190+
```
191+
selected members: eui-neo-app-main eui-neo-window eui-neo-markdown \
192+
eui-neo-sdl2 eui-neo-vulkan eui-neo
193+
194+
workspace (linux) pass 12m26s
195+
workspace (macos) pass 6m15s
196+
workspace (windows) pass 7m50s
197+
```
198+
199+
The `app-main` line on each leg is the assertion that matters, and it is
200+
self-proving:
201+
202+
```
203+
compat.eui-neo[app-main]: linked, main() supplied by the package; window run is opt-in
204+
```
205+
206+
The test TU defines no `main`, so the binary can only run if `glfw_app_main.o`
207+
supplied one. Printing that line at all therefore proves the feature's source
208+
compiled and linked — on Windows and macOS for the first time ever, which is what
209+
exercises the two additions below.
210+
211+
Two things were new there and were the reason to watch the first run:
190212
191213
* `glfw_app_main.cpp` has never been compiled on any platform, so its Windows half
192214
is newly exercised. Two descriptor additions came out of auditing it, both

0 commit comments

Comments
 (0)