ktools language-aligned tools, one static reference site
Language Page

kbuild for Java

This page is assembled from markdown in ktools-java. GitHub links point to the workspace repo and the relevant source files or directories.

2 markdown sections
QM-Code/ktools-java primary repo
HTML static output
ktools-java

kbuild for Java

Canonical markdown for kbuild in the ktools-java workspace.

Java ktools-java main
C++ C# Java JavaScript Kotlin Python Rust Swift

kbuild` In `ktools-java

ktools-java/docs/kbuild.md

The Java workspace currently uses the shared kbuild command model rather than a checked-in Java-local kbuild/ tree.

Current Status

  • the workspace expects kbuild on PATH
  • batch orchestration and build flow should stay compatible with the shared kbuild repo
  • the Java workspace pages document the current usage model, not a separate implementation

Kbuild Documentation

kbuild/docs/index.md

kbuild is a strict Python build and repo orchestration tool for ktools-style projects. It handles five related jobs:

  • creating and validating repo-local kbuild config
  • building core targets into named build slots
  • building ordered demo trees against the core SDK and dependency SDKs
  • scaffolding and helper operations such as repo initialization, git setup, and repo-local vcpkg
  • batch-forwarding commands into child repos

Start Here

Typical Flow

Fresh directory:

kbuild --kbuild-config
# edit .kbuild.json
kbuild --kbuild-init
kbuild --vcpkg-install

Existing repo:

kbuild --build-latest
kbuild --build-demos
kbuild --clean-latest

kbuild selects exactly one backend from the repo config. The shared tree currently supports:

  • cmake
  • cargo
  • java
  • swift
  • kotlin
  • csharp
  • javascript

Core Concepts

Repo root

  • kbuild only runs from a directory containing ./.kbuild.json.

Primary config

  • ./.kbuild.json is the required repo marker and primary config file.

Optional shared base

  • ./kbuild.json is optional. When present, kbuild deep-merges ./.kbuild.json on top of it.

Build slots

  • Core builds live under build/<slot>/.
  • Demo builds live under demo/<demo>/build/<slot>/.
  • The default slot is latest.

SDK-first demos

  • Root builds install an SDK under build/<slot>/sdk.
  • Demos consume that SDK, optional dependency SDKs, and optionally earlier demo SDK outputs in the requested order.

Repo-local vcpkg

  • When the effective config defines vcpkg, kbuild expects a repo-local checkout under ./vcpkg/src and integrates it through CMake manifest mode.

Which Command Should I Reach For?

  • Use kbuild --build-latest for the normal build path.
  • Use kbuild --build-demos when you want explicit demo validation.
  • Use kbuild --cmake-no-configure only for cmake repos when the target build directory already contains CMakeCache.txt.
  • Use kbuild --vcpkg-install only for cmake repos the first time a repo-local vcpkg project is prepared.
  • Use kbuild --git-initialize only once, after scaffold generation and remote creation.

Working References

If you want the code behind the behavior, start with:

If you want the exhaustive CLI and schema rules, use the full operator reference.