openembedded

问题 What is the correct way of adding custom commands to u-boot in a Yocto setup (currently using Petalinux 2016.4 by Xilinx)? Should I add the relevant source files to the u-boot source through a recipe/patch, to be included in the compilation of u-boot? Is there a better way to do this during development to get a faster turn around. In what folder should the code be placed - under u-boot/board or added to u-boot/commands? Thanks 回答1: IMHO you have two options for adding the additional

问题 I was trying to build apache2 on yocto. But I was getting below errors. ERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. Rerun configure task after fixing this. Some googling led me to https://lists.yoctoproject.org/pipermail/yocto/2012-March/005125.html So I looked into conf.log and find out those lines: cc1: warning: include location "/usr/local/include" is unsafe for cross-compilation [-Wpoison-system

问题 I am trying to build a yocto demo-coreip-cli image for my custom risc-v SOC which only supports imafd instructions. For the compilation of cross toolchain that is used by Bitbake, I tried changing cross-binutils.inc recipe and cross-gcc.inc recipe in openembedded-core layer by including “ –with-arch=rv64imafd ” in " EXTRA_OECONF " variable. Is there anything else I am missing or doing wrong? Thank You. 回答1: I was able to successfully port the image to RV64-imafd. You can follow this link for

问题 I'm creating quite a simple Yocto image based on x86. I want the / file system to be readonly, so I set the IMAGE_FEATURES_append = " read-only-rootfs " in a custom copy of the original core-image-minimal.bb . I do want to have the /home writable and on a separate partition, though. So, I'm adding a line part /home --ondisk sda --fstype=ext4 --label home --align 1024 --size 600 in genericx86.wks. This creates the actual /home partition in the final wic image, but it naturally does not hold

问题 I'm creating quite a simple Yocto image based on x86. I want the / file system to be readonly, so I set the IMAGE_FEATURES_append = " read-only-rootfs " in a custom copy of the original core-image-minimal.bb . I do want to have the /home writable and on a separate partition, though. So, I'm adding a line part /home --ondisk sda --fstype=ext4 --label home --align 1024 --size 600 in genericx86.wks. This creates the actual /home partition in the final wic image, but it naturally does not hold

问题 I am observing that the yocto build system is just applying my patch instead of applying and committing the patch on the cloned git repo. Original bitbake ( u-boot-ti-staging_2018.01.bb ) file. require u-boot-ti.inc PR = "r19" BRANCH = "ti-u-boot-2018.01" SRCREV = "8b2f1df4b55bc0797399a21d42ac191d44f99227" Modified bitbake file, added SRC_URI to the file. require u-boot-ti.inc PR = "r19" BRANCH = "ti-u-boot-2018.01" SRCREV = "8b2f1df4b55bc0797399a21d42ac191d44f99227" SRC_URI += "file://0001

问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe