Skip to content

Conversation

@dwagenk
Copy link

@dwagenk dwagenk commented Sep 4, 2025

NOTE This is meant for discussion. This implementation evolved over the past few years and I've used it in multiple projects. The image_populate_mfgtool class did not exist when I first used this class. Are you interested in integrating this into meta-freescale?

The uuu_bundle.bbclass can be used to create uuu zip files containing arbitrary files collected from DEPLOY_DIR_IMAGE and a uuu.auto script. A user provided uuu.auto.in script is processed to replace file placeholders and text placeholders.

The uuu_image_bundle.bbclass does the same for image recipes when inheriting the class and specifying a basetype with uuu-zip extension in IMAGE_FSTYPE, e.g. ext4.gz.uuu-zip. This can be done for multiple basetypes, so the same image recipe can provide different uuu-bundles, e.g. for booting the image from ramdisk for test purposes or flashing it to internal storage.

The provided classes differ from the image_populate_mfgtool.bbclass by:

  • not being limited to image recipes
  • allowing creation of uuu bundles for multiple types from IMAGE_FSTYPES
  • not bundling the uuu binaries
  • creating a name.uuu.zip file that can be directly used with the uuu tool, e.g. uuu path/to/name.uuu.zip
  • more flexible variable replacement, e.g. not assuming UBOOT_BINARY is used as bootloader in uuu.auto script
  • properly integrating with the Openembedded deploy and image deploy mechanisms
  • different semantics

The uuu_bundle.bbclass can be used to create uuu zip files containing
arbitrary files collected from DEPLOY_DIR_IMAGE and a uuu.auto script.
A user provided uuu.auto.in script is processed to replace file
placeholders and text placeholders.

The uuu_image_bundle.bbclass does the same for image recipes when
inheriting the class and specifying a basetype with `uuu-zip` extension
in IMAGE_FSTYPE, e.g. `ext4.gz.uuu-zip`. This can be done for multiple
basetypes, so the same image recipe can provide different uuu-bundles,
e.g. for booting the image from ramdisk for test purposes or flashing it
to internal storage.

The provided classes differ from the image_populate_mfgtool.bbclass by:
- not being limited to image recipes
- allowing creation of uuu bundles for multiple types from IMAGE_FSTYPES
- not bundling the uuu binaries
- creating a name.uuu.zip file that can be directly used with the uuu
  tool, e.g.
    uuu path/to/name.uuu.zip
- more flexible variable replacement, e.g. not assuming `UBOOT_BINARY`
  is used as bootloader in uuu.auto script
- properly integrating with the Openembedded deploy and image deploy
  mechanisms
- different semantics

Signed-off-by: Daniel Wagenknecht <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant