mcpp.toml

# openarch's aarch64 backend: instructions, and nothing else.
#
# ⚠️ THIS PACKAGE EXPORTS NO MODULE. It defines the C entry points declared in
# `abi/include/openarch/abi.h` and is reached only through them. A consumer
# never names it: the root manifest pulls it in through the `backend` feature,
# whose target-conditional `feature-deps` row selects this one.
#
# The separation is what lets a second implementation of the same ABI exist
# without touching the specification: a vendor's assembler file, a simulator's
# shim, or a second backend for the same ISA at a different privilege level.
# riscv needs that last one — this backend traps into M-mode, and a kernel
# running under SBI traps into S-mode, which is the same mechanism with a
# different prefix on every register and therefore a different backend.
[package]
namespace   = "mcpplibs"
name        = "openarch-aarch64"
version     = "0.5.0"
description = "openarch's aarch64 backend: the instructions behind the ABI"
license     = "Apache-2.0"
authors     = ["mcpplibs"]
repo        = "https://github.com/mcpplibs/openarch"

# ⭐ THE CAPABILITY, NOT THE PACKAGE NAME, IS WHAT A CONSUMER BINDS TO. The root
# package's `backend` feature requires `openarch-backend` and names nobody; the
# resolver binds the one provider in the graph. A consumer's own implementation
# of `openarch/abi.h` declares the same line and is selected the same way.
provides    = ["openarch-backend"]

[build]
sources = ["src/**"]

[targets.openarch-aarch64]
kind = "lib"

[dependencies]
openarch-abi = { path = "../../abi" }