pub struct RecipeSpec {
pub recipe_name: String,
pub deploy_root: String,
pub app_bin: String,
pub firmware: Vec<String>,
pub ta: Option<String>,
pub has_www: bool,
pub systemd_unit: String,
pub dts_files: Vec<String>,
pub boot_files: Vec<String>,
}Expand description
The on-target install manifest for a generated .bb recipe.
Built from the pipeline’s resolved outputs and used to render a self-contained
Yocto recipe that installs the assembled dist/ tree. All artifact fields are
bare file names under the corresponding dist/ subdirectory (e.g. app.elf
lives at dist/app/app.elf).
Fields§
§recipe_name: StringThe recipe/package name (PN); also the .bb file stem.
deploy_root: StringOn-target install prefix from [profile] deploy_root (e.g. /opt/consortium).
app_bin: StringThe application binary file name under dist/app/.
firmware: Vec<String>Firmware ELF file names under dist/firmware/ (e.g. cm33.elf).
ta: Option<String>The signed TA file name under dist/ta/, when present.
has_www: boolWhether an HMI dist/www/ tree was assembled.
systemd_unit: StringThe systemd unit file name under dist/systemd/ (e.g. consortium-app.service).
dts_files: Vec<String>Device-tree file names under dist/dts/linux/: a .dtso overlay is
installed into the rootfs (applied at runtime via configfs); a merged
.dts is a kernel build input, staged but not installed.
boot_files: Vec<String>Boot-args file names under dist/boot/ (e.g. boot.cmd,
extlinux-uio.cfg, README). These are bootloader/image inputs, staged
for the integrator but not installed into the rootfs.