Quicken Build · GoForge

Quicken Build is the Go+ target and toolchain boundary for applications built with Cadence and Quicken. A versioned quicken.yaml manifest declares application identity, entry packages, deployment versions, and target policy.

go install goforge.dev/quicken/build/cmd/quicken-build@v0.4.0

quicken-build \
  -module example.com/myapp \
  -name MyApp \
  -appid com.example.myapp \
  init ./myapp

quicken-build doctor all
quicken-build build web
quicken-build build desktop
quicken-build run ios-simulator
quicken-build run android-emulator

Targets

Family	Targets
Browser	WebAssembly and server
Terminal	Host TUI
Desktop	Windows, macOS, Linux on amd64 and arm64
Apple	iOS simulator and iOS device
Android	Emulator and device identities with SDK diagnostics

The iOS path directly targets iphonesimulator, including native Apple Silicon arm64, then signs, installs, and launches the application. It does not rely on gogio’s obsolete CPU-to-platform inference.

Android remains configured even before its SDK/NDK is installed. Doctor and run commands report the exact missing tools; APK packaging is the next implementation milestone and is not claimed by this release.

Version v0.2.0 adds a distinct iphoneos device build, optional provisioning and signing, devicectl installation/launch, and explicit per-architecture desktop C/C++ toolchains for Gio cross-builds.

Version v0.3.0 adds a generated full-stack Go+ starter with checked-in generated Go, Cadence logic, shared semantic and browser views, WebAssembly and server entry points, TUI, Desktop, Mobile, quicken.yaml, and GoForge tasks. The generated iOS and Android adapters use their platform idiom profiles.

Version v0.4.0 completes the artifact matrix: server and TUI executables for Windows, macOS, and Linux on amd64 and arm64, plus per-target C/C++/linker configuration for Gio desktop builds. The starter preconfigures both macOS architectures; Windows and Linux GUI cross-builds use the declared native toolchains and libraries.