Files
rajamesandClaude Opus 5.5 92ca805ecf
StarshipOS Build / milkv (pull_request) Failing after 38s
StarshipOS Build / pc (pull_request) Failing after 34s
StarshipOS Build / pi4 (pull_request) Failing after 35s
StarshipOS Build / pi5 (pull_request) Failing after 35s
StarshipOS Build / qemu (pull_request) Failing after 34s
StarshipOS Build / Isabelle/HOL Proofs (pull_request) Failing after 1m30s
StarshipOS Build / Documentation (pull_request) Failing after 37s
Merge master into StarForth-v4.0.0: the branch's build, master's CI files kept
For PR #30. master's 9 commits since the fork (T= board selection,
mk/boards.mk, build.yml, the nightly workflows) conflicted in four
files; each is resolved to the branch's version:

  .gitea/workflows/nightly.yml       added on both; master's copy named
  .gitea/workflows/nightly-docs.yml  the branch in its checkout, the
                                     branch's builds the default branch
  Makefile                           master's T= and mk/boards.mk against
  kernel/Makefile                    the branch's TARGET=<board> and
                                     boards/; master's edits were to
                                     Makefile.starkernel, renamed here

The two workflows' header comment now says they build master.

Merged cleanly from master: build.yml (its board matrix, Nexus publish
and 02:00 nightly; it still calls Makefile.starkernel and make
T=<board>, which this tree does not have -- #18) and mk/boards.mk
(nothing here includes it).

Against the branch the merge changes only those CI files and
mk/boards.mk: no kernel, v4 or Makefile source, so the build is the one
accepted on 2026-11-06.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
2026-11-06 16:08:22 +00:00
..

mk/

  • Kconfig.mk — shared Kconfig bridge included by both Makefile and kernel/Makefile. Each Makefile canonicalizes its own ARCH and sets KCONFIG_ARCH_DIR before including this file, since the hosted and kernel builds map aarch64 to different object-directory names. Config lives per-architecture under build/$(KCONFIG_ARCH_DIR)/ rather than a single root .config, because this project's QEMU acceptance workflow builds all three kernel architectures back-to-back in one script — a shared root .config would desync from whichever arch is actually being built. Provides the kconfig_bool/kconfig_int macros that let each -D knob repoint from a bare historical default to the Kconfig-fed CONFIG_* value one knob family at a time, preserving today's behavior exactly whenever no .config is present yet.

See configs/ for example defconfig files and tools/kconfig/ for the vendored Kconfig tooling this bridge drives.