Yocto:CORE_IMAGE_EXTRA_INSTALL和IMAGE_INSTALL之间的区别 [英] Yocto: Difference between CORE_IMAGE_EXTRA_INSTALL and IMAGE_INSTALL

问题描述

最近，我试图通过Yocto版本将开源软件包(iperf3)包含到目标图像中.(将IMAGE_INSTALL + ="iperf3"的local.conf更新为项目已经对应的配方).但是最终映像未包含在根文件系统中.我尝试通过添加到/recipe-core/packagegroups/RDEPENDS_packagegroup *的程序包组配方中来进行同样的操作，并能够成功地将其包含在内.

有人可以为我提供这种行为的解释吗?

解决方案

在local.conf中写入 IMAGE_INSTALL + ="iperf3" 时，将立即添加 iperf3 转到 IMAGE_INSTALL .如果您的映像通过执行 IMAGE_INSTALL?=".... "添加基本rootfs，则该默认值将永远不会添加，因为 IMAGE_INSTALL 已经具有一个值./p>

如果您想从local.conf(和许多其他变量)中修改 IMAGE_INSTALL ，则应始终使用延迟的添加/前缀进行此操作.即

  IMAGE_INSTALL_append ="iperf3" 

注意前导空格.

Recently, i tried to include open source package (iperf3) to target image via Yocto build. (Updating local.conf for IMAGE_INSTALL += "iperf3" , as the project already corresponding recipe). But the final image did not include in root file system. I tried the same by adding to package group recipe in /recipe-core/packagegroups/RDEPENDS_packagegroup* and was able to include it successfully.

Can someone provide me explanation for the behavior.

解决方案

When you write IMAGE_INSTALL += "iperf3" in your local.conf, that will immediately add iperf3 to IMAGE_INSTALL. If your image adds the base rootfs by doing IMAGE_INSTALL ?= "....", then that default value will never be added, as IMAGE_INSTALL already have a value.

If you want to modify IMAGE_INSTALL from local.conf (and a lot other variables), you should always do that with a delayed append / prepend. I.e.

IMAGE_INSTALL_append = " iperf3"

Note the leading space.

这篇关于Yocto:CORE_IMAGE_EXTRA_INSTALL和IMAGE_INSTALL之间的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！