apkg-build

A package build system for Azusa OS. This tool automates the process of downloading, building, and packaging software into SquashFS archives for the Azusa package management system.

• Multiple build engines: Supports autoconf, CMake, Meson, and custom build scripts
• Automatic engine detection: Detects the appropriate build system from source files
• Cross-architecture builds: Build packages for amd64, 386, and arm64 via QEMU
• Reproducible builds: Uses SOURCE_DATE_EPOCH and deterministic archive options
• Smart caching: Downloads are cached locally and mirrored to S3
• Automatic organization: Separates output into core, libs, dev, doc, and fonts subpackages

go build -o apkg-build .

# Update the recipe repository
apkg-build update

# Build a package by name
apkg-build build zlib

# Build a package by category/name
apkg-build build sys-libs/zlib

# Build a specific version
apkg-build -version 1.2.13 build sys-libs/zlib

# Build for a different architecture
apkg-build -arch arm64 build sys-libs/zlib

apkg-build uses recipes from the azusa-opensource-recipes repository. The repository is automatically cloned to one of these locations:

• $HOME/apkg-recipes
• $HOME/projects/apkg-recipes
• $HOME/.cache/apkg-recipes
• /tmp/apkg-recipes

Each package recipe is a directory containing:

category/package-name/
├── build.yaml      # Build configuration
├── metadata.yaml   # File hashes (auto-generated)
├── azusa.yaml      # Optional package metadata
└── files/          # Patches and additional files
    └── *.patch

versions:
  list:
    - "1.0.0"
    - "1.1.0"
    - "1.2.0"
  stable: "1.2.0"

build:
  - version: "1.*"              # Version pattern (glob)
    source:
      - "https://example.com/pkg-1.2.0.tar.gz"
      - "https://example.com/extra.zip -> extra.zip"  # Rename syntax

    patches:
      - "001-fix-build.patch"   # From files/ directory

    engine: "autoconf"          # autoconf, cmake, meson, none, or auto

    options:
      - autoreconf              # Run autoreconf -fi
      - light                   # Skip standard configure flags
      - build_in_tree           # Build in source directory

    arguments:
      - "--enable-shared"
      - "--disable-static"

    env:
      - "CFLAGS=-O2"
      - "S=${WORKDIR}/custom-dir"  # Override source directory

    import:
      - "sys-libs/zlib:1.2"     # Package dependency with version
      - "libpng"                # pkg-config dependency

    # Build hooks (shell commands)
    configure_pre: []
    configure_post: []
    compile_pre: []
    compile_post: []
    install_pre: []
    install_post: []

For packages without a build.yaml, apkg-build supports legacy shell scripts. These are self-contained bash scripts that handle the entire build process.

Scripts are named {package}-{version}.sh (e.g., zlib-1.0.8.sh) and placed in the package directory:

category/package-name/
├── zlib-1.0.8.sh
├── zlib-1.2.13.sh
└── files/
    └── patches...

Shell scripts source common/init.sh which provides helper functions:

#!/bin/sh
source "../../common/init.sh"

get https://example.com/source.tar.gz    # Download and extract
acheck                                     # Verify build environment

cd "${T}"                                  # Change to temp build dir
importpkg sys-libs/zlib                   # Import dependencies
doconf --enable-shared                    # Run configure
make -j${NPROC}                           # Build
make install DESTDIR="${D}"               # Install

finalize                                   # Run fixelf, organize, archive

Standard GNU Autotools build:

./configure --prefix=... && make && make install

Options:

• autoreconf: Run autoreconf -fi before configure
• light: Skip standard configure flags
• 213: Skip --docdir flag (for older autoconf)
• build_in_tree: Build in source directory instead of separate build dir

CMake with Ninja generator:

cmake -G Ninja ... && ninja && ninja install

Meson build system:

meson setup ... && ninja && ninja install

No automatic build commands. Use hooks (compile_pre, install_pre, etc.) to define custom build steps.

The following variables are available in build.yaml and hooks:

Built packages are organized into subpackages:

Output location:

• SquashFS files: /tmp/apkg/
• If running as root: Also copied to /var/lib/apkg/unsigned/

For non-native architectures, apkg-build automatically launches a QEMU virtual machine:

• amd64/386: Uses KVM acceleration (8GB RAM)
• arm64: Software emulation (2GB RAM)

QEMU VMs are configured with:

• Temporary disk image for build artifacts
• SSH access for remote command execution
• Network access for package downloads

• Go 1.16+
• For local builds:
  • Standard build tools (gcc, make, etc.)
  • mksquashfs
• For QEMU builds:
  • QEMU with KVM support
  • Azusa kernel and initrd

See the Azusa OS project for licensing information.