fe6462088a
Clients connect over a Unix socket, are handed a shared buffer, draw into it and commit; Schcom composites and presents. Both of the hard blockers its README listed -- unix domain sockets and raw input events -- have been done for a while, so nothing was in the way. The model is Wayland's, on purpose. A surface is not a window: it is a rectangle of pixels with no policy attached, because placement belongs to SchWM and the moment this program starts deciding where windows go the split has failed. Nothing is shown until COMMIT, so a client halfway through drawing is never presented. The compositor tells clients when to draw rather than letting them render frames nobody sees. Wayland is MIT-licensed and supporting it later is intended, so the divergences are the ones that are cheap to undo: a buffer handle is a System V shm id rather than an fd over SCM_RIGHTS, and the message carries a handle_kind field so switching is a new value rather than a protocol break. Every message carries its own length, so an unknown message is skipped instead of desynchronising the stream -- which is what lets a v0 compositor survive a v1 client. The compositor owns the shm segment, not the client: it has to survive a client crashing mid-frame, and it must not be something a client can resize underneath it. A dropped connection takes its surfaces and their segments with it. Composites into a back buffer and copies once, because compositing straight into the framebuffer shows every intermediate state -- the flicker would be the whole desktop being repainted under the user's eyes. projects/ gets build glue for the first time: `make projects` builds against the sysroot's libc and stages into sysroot/bin. It is not a dependency of anything above it, and `make` never descends there. Verified by `make schcom-test`, which boots SchOS, runs the compositor and a client, screendumps the framebuffer and asserts the pixels on the host. That last part is the point -- the compositor reporting that it composited something proves nothing, and a screenshot nobody inspects proves less. It checks the client's colour mid-surface, the compositor's background, and the white border exactly at the requested origin, so "arrived" and "arrived at the wrong offset" cannot pass for each other. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
32 lines
770 B
Makefile
32 lines
770 B
Makefile
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
# Schcom builds like any other program that runs *on* SchOS: against the
|
|
# sysroot's libc, never against kernel headers. The top-level Makefile passes
|
|
# CC, CFLAGS and DESTDIR in; nothing here reaches back up the tree.
|
|
#
|
|
# It is not part of the OS build. `make` at the top level never descends here --
|
|
# `make projects` does.
|
|
|
|
CC ?= cc
|
|
CFLAGS ?= -O2
|
|
CFLAGS += -Wall -Wextra -std=c11
|
|
DESTDIR ?= ../../sysroot
|
|
|
|
BINS = schcom schcom-demo
|
|
|
|
all: $(BINS)
|
|
|
|
schcom: schcom.c proto.h
|
|
$(CC) $(CFLAGS) -o $@ schcom.c $(LDFLAGS)
|
|
|
|
schcom-demo: schcom-demo.c proto.h
|
|
$(CC) $(CFLAGS) -o $@ schcom-demo.c $(LDFLAGS)
|
|
|
|
install: $(BINS)
|
|
mkdir -p $(DESTDIR)/bin
|
|
cp $(BINS) $(DESTDIR)/bin/
|
|
|
|
clean:
|
|
rm -f $(BINS)
|
|
|
|
.PHONY: all install clean
|