Getting Started with Hera
Build the daemon and its client libraries, understand the target environment, and choose an application toolkit.
Hera's production display path uses Vulkan and DRM/KMS on Linux. To produce consistent binaries for that environment, the repository builds against an explicit Buildroot SDK inside a builder container. You can use macOS for supported development and IPC work, but changes involving physical presentation still need verification on the Linux display path.
Build the Target Artifacts
Run the repository build from its root:
podman run --rm \
-v "$PWD":/work \
hera-builder:latest \
bash -lc 'cd /work && ./build.sh'Before running this command, make sure the builder image contains the required toolchain and SDK. The build.sh entry point delegates to scripts/build_hera.py, which validates the SDK, builds the selected workspace packages for aarch64-unknown-linux-gnu, and installs the resulting artifacts into system/bin.
Run ./build.sh --help in the same environment to inspect the available SDK and build-profile options. Choose --release when you need optimized artifacts, or add --offline when the builder must use only cached Cargo dependencies. An offline build requires those dependencies to be present before it starts.
Installed Artifacts
The installed files include herad, mockherad, libhera_ffi.so, and the applications selected by the build script. Their supporting assets, font manifests, licenses, and launch scripts are installed alongside them. Preserve that relative layout when copying the installation to a device so that application launchers and manifests can still locate their files.
The FFI library is consumed by native clients such as rn_host. Build Hera before configuring a downstream native client, and ensure that the client's headers and library come from compatible source revisions.
Prepare the Display Environment
On the device, the daemon needs access to the DRM and input devices, a compatible Vulkan driver, and the runtime libraries required by the selected applications. Since the daemon owns the output and presentation resources, applications connect to its socket rather than opening the display device themselves.
Read configuration before changing device selection or presentation mode. Use the app-owned launch scripts for an existing application so that font and library configuration matches the deployed assets.
Build Your First Interface
Follow Hera Kit getting started for a complete Rust entry point. Follow React Native setup when integrating an existing JavaScript application.
If startup succeeds but the display is empty, work through troubleshooting. Diagnose connection setup, scene acceptance, submission, and presentation separately.
Source Reference
The following files in the Hera checkout define the behavior described on this page.
build.shscripts/build_hera.pyapps/herad/src/main.rs