nexoniarz/SchOS
nexoniarz/SchOS
Watch
1
0
Fork
You've already forked SchOS
 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions
SchOS/.claude/memory/schunix-build-environment.md
Nexoniarz 57aff40228 docs: four directories, and a rule for when a thing leaves the roadmap 
docs/ was ten files where a plan, a description, a guide and a bug report all
sat next to each other. It is now architecture/ (what SchOS is), plan/ (what it
will be), guides/ (how to work on it) and history/ (why it is like this), with
an index that states the one rule holding it together: when something is
finished it moves from plan/ to architecture/ and is rewritten as a description
of the thing rather than a record of building it.

A ticked checkbox says the work happened. It does not say what the work
*produced*, and six months later the checkbox is all that is left. The network
stack proved the point: finished, verified end to end, and for a month the only
description of it anywhere was a checkbox four levels of indentation deep.

So roadmap.md went from 534 lines to 181 -- nothing deleted, the done work
graduated. Seven subsystems that were finished and undescribed now have
descriptions: boot, kernel, syscalls, filesystem, networking, graphics, usb,
init. Every one ends with "What it does not do", which is the section that pays;
a document listing only strengths is marketing, and the reader who needs it most
is the one about to trip over a limitation nobody wrote down.

schfs.md still opened with "phases 1 through 3 1/2 are done, phase 4 is next"
long after all five had landed. It is a description now, with the phase record
and the hard-won bugs moved to history/.

Three corrections found on the way, all load-bearing:

  * projects/schcom/README.md claimed SCM_RIGHTS was done. There is no
    sendmsg/recvmsg in the kernel at all, and an entire GUI plan rested on it.
  * The root README said "No TCP/IP" months after the stack landed.
  * history/kernel.md sec.7 was marked "in progress" on a problem that process
    groups solved.

Also adds plan/1.0.md, which draws a finish line so the open list stops being
infinite, and marks schwm/ and schde/ superseded: in Wayland the compositor is
the window manager, so that split dissolves rather than being abandoned.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2
2026-09-12 17:13:35 +02:00

2.9 KiB
Raw Blame History

name description metadata
schunix-build-environment Schunix builds natively on Windows with clang/lld + mingw + Git Bash; WSL is gone because WSL2 needs Hyper-V
node_type type originSessionId modified
memory project 9d8a2aef-bcf0-47a0-96c6-f706efab4a95 2026-08-07T17:19:34.188Z

Builds natively on Windows. WSL is no longer used at all. WSL2 runs a real Linux kernel in a Hyper-V VM, so it hard-requires virtualisation, and enabling that puts the Hyper-V hypervisor under the whole machine — which demotes VMware to running nested and slows the box down permanently. Nexoniarz will not enable it, and that is a reasonable call.

make from Git Bash does everything. run.ps1 builds natively too. The toolchain, all already installed:

  • clang + ld.lld + llvm-objcopy/objdump (C:\Program Files\LLVM\bin) — clang is a cross-compiler by construction, so --target=x86_64-elf builds the kernel and --target=i386-elf the bootloader. No cross-binutils needed.
  • mingw-w64 gcc (scoop install mingw) for host tools — tools/mkfs.c needs <unistd.h>/<dirent.h>, which the Windows SDK lacks.
  • make (scoop install make), plus Git Bash's perl/sed/dd/sha256sum.

run.ps1 prepends all three directories itself, so it works from any shell. The Makefile detects Windows via uname -s matching MINGW* and sets WINHOST. Ports (musl/mksh/toybox) are not rebuilt on Windows — they are Linux userland built by configure scripts, already staged in sysroot/, and the Makefile says so out loud rather than skipping silently. Everything is a no-op on Linux, so a Linux/VM build still works identically.

Five latent bugs the move exposed, all real, none Windows-specific — see docs/history/kernel.md §8 for the two hardest:

  1. kernel.ld named no .ltext/.ldata/.lbss — with -mcmodel=large, LLVM and GCC 13+ put nearly everything there, and orphan placement put them past end, so kinit1(end,...) handed the allocator live .lbss.
  2. uint64 was unsigned long — 64-bit on Linux, 32-bit on Windows (LLP64). Host tools include the on-disk structs, so this would have silently written images with half-width inode fields. Now data-model-aware + _Static_assert.
  3. syscall_entry used %fs:(0) as scratch — that is the TCB self-pointer. GCC's direct %fs:-8 TLS never reads it; clang materialises the TP from it.
  4. _start read argc/argv via register ... asm("rdi"), which is only guaranteed for inline-asm operands. clang read uninitialised stack. Now lib/start.S.
  5. lld needs --image-base=0 for anything linked below 0x400000, and -m elf_x86_64 on ld -r -b binary.

When a symptom moves as you add printfs, stop printing and use the watchpoint. QEMU -S -gdb tcp::26000 plus mingw's gdb (hbreak, then watch) named the offending instruction on the first run after three rounds of cprintf had failed. See schunix-verify-by-driving-shell.