From: Khairul Rohaizzat Jamaluddin <[email protected]>
IMAGE_EFI_BOOT_FILES created to help differentiate files needed between bootimg-efi and bootimg-partition when creating the installer/.wic file. Signed-off-by: Khairul Rohaizzat Jamaluddin <[email protected]> --- documentation/ref-manual/ref-variables.xml | 55 ++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index a506480..6e438e8 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -5719,6 +5719,61 @@ </glossdef> </glossentry> + <glossentry id='var-IMAGE_EFI_BOOT_FILES'><glossterm>IMAGE_EFI_BOOT_FILES</glossterm> + <info> + IMAGE_EFI_BOOT_FILES[doc] = "A space-separated list of files from ${DEPLOY_DIR_IMAGE} to place in EFI boot partition." + </info> + <glossdef> + <para role="glossdeffirst"> + A space-separated list of files installed into the + EFI boot partition when preparing an image using the Wic tool + with the <filename>bootimg-efi</filename> source + plugin. + By default, the files are installed under the same name as + the source files. + To change the installed name, separate it from the + original name with a semi-colon (;). + Source files need to be located in + <link linkend='var-DEPLOY_DIR_IMAGE'><filename>DEPLOY_DIR_IMAGE</filename></link>. + Here are two examples: + + <literallayout class="monospaced"> + IMAGE_EFI_BOOT_FILES = ${IMGDEPLOYDIR}/${IMAGE_BASENAME}-${MACHINE}.ext4;rootfs.img + </literallayout> + </para> + + <para> + Alternatively, source files can be picked up using + a glob pattern. + In this case, the destination file must have the same name + as the base name of the source file path. + To install files into a directory within the + target location, pass its name after a semi-colon + (;). + Here are two examples: + <literallayout class="monospaced"> + IMAGE_BOOT_FILES = "boot/loader/*" + IMAGE_BOOT_FILES = "boot/loader/*;boot/" + </literallayout> + The first example installs all files from + <filename>${DEPLOY_DIR_IMAGE}/bcm2835-bootfiles</filename> + into the root of the target partition. + The second example installs the same files into a + <filename>boot</filename> directory within the + target partition. + </para> + + <para> + You can find information on how to use the Wic tool in the + "<ulink url='&YOCTO_DOCS_DEV_URL;#creating-partitioned-images-using-wic'>Creating Partitioned Images Using Wic</ulink>" + section of the Yocto Project Development Tasks Manual. + Reference material for Wic is located in the + "<ulink url='&YOCTO_DOCS_REF_URL;#ref-kickstart'>OpenEmbedded Kickstart (.wks) Reference</ulink>" + chapter. + </para> + </glossdef> + </glossentry> + <glossentry id='var-IMAGE_BOOT_FILES'><glossterm>IMAGE_BOOT_FILES</glossterm> <info> IMAGE_BOOT_FILES[doc] = "A space-separated list of files from ${DEPLOY_DIR_IMAGE} to place in boot partition." -- 2.7.4
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142634): https://lists.openembedded.org/g/openembedded-core/message/142634 Mute This Topic: https://lists.openembedded.org/mt/76907467/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
