How about adding in your busybox bbappend file the following line. DEPENDS += "libtirpc" Best Regards, Chen Qi

This is because prelink_image is also in IMAGE_PREPROCESS_COMMAND. meta/classes/image-prelink.bbclass:IMAGE_PREPROCESS_COMMAND_append_libc-glibc = " prelink_setup; prelink_image; " And as it's using _

The above issue has been filed a bug in bugzilla. https://bugzilla.yoctoproject.org/show_bug.cgi?id=13047 I've also added my comments there. Best Regards, Chen Qi

For the current codes, manually creating symlink is the easiest way to achieve your goal. The current mechanism in systemd.bbclass has to 'enable' or 'disable' all services in SYSTEMD_SERVICE_xxx. The

Check the packages-split/ directory to see how files are put in each package. I guess these files are packages into other packages derived from the ncurses recipe. Best Regards, Chen Qi

The current logic for checking cve tag is not correct. It errors out if and only if the patch contains a line which begins with CVE-YYYY-XXXX and contains nothing else. It will not error out if the pa

I guess the problem is about LIC_FILES_CHKSUM. Your LICENSE is set to 'Zoli'. So where do you put your Zoli license and what's the checksum of it? How about using the following two lines if you do not

Hi Aaron, The main pain for now is that `devtool sdk-install <DEPEND_RECIPE>' does not work as expected, right? I just checked the codes of sdk-install, and found that it does not fit the current RSS

I think the main problem is do_fetch sig mismatch. What does the SRC_URI for the recipe look like? Best Regards, Chen Qi

This is the current RDEPENDS setting in kernel-devsrc.bb recipe: RDEPENDS_${PN} = "bc python flex bison ${TCLIBC}-utils" # 4.15+ needs these next two RDEPENDS RDEPENDS_${PN} += "openssl-dev util-linux

In case of the existence of meta-mingw, the library is .dll instead of .so and these .dll files are in ${bindir}. We need to check the existence of the .so file before doing readlink, otherwise do_ins

Which recipe and what configuration?

I'd suggest you not using precompiled SDK unless you are justing doing some simple cross compilation that requires no additional libs, header files, etc. The populate_sdk task directly installs rpm pa

I just checked out v230 and took a look of the codes. I think it's the codes below that raise the 'No medium found' error. src/basic/cgoup-util.c int cg_unified(void) { struct statfs fs; /* Checks if

How about using SDK_POSTPROCESS_COMMAND? Best Regards, Chen Qi

The problem is about two machines having the same TUNE_PKGARCH, and could be solved by setting TOOLCHAIN_OUTPUTNAME in your distro conf file to include MACHINE information. But I'm not sure if this is

I think using IMAGE_INSTALL_append = " curl", and then `bitbake core-image-minimal -c populate_sdk_ext" is sufficient. After this, you can develop against curl libs/headers inside the sdk. Best Regard

The tmp/ directory. Best Regards, Chen Qi

The SERIAL_CONSOLES setting is _expected_ affect all recipes. That's why it's usually set in some .conf file. Serial consoles will have different names and are device related. That's why we have the v

There is a separate directory, which is usually downloads/ under the build directory, to keep downloaded git repos and tarballs. [network] ---> [downloads] ---> [tmp/work/xxxx] So you don't have to wo