Hi Scott, IMAGE_INSTALL is the way to go. I recommend spending some time on watching https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj Here you'll learn that you shouldn't reall

Hi, I also see that there's only a kernel recipe. IIRC, kirkwood devices are supported in upstream linux, so you're probably fine using linux-yocto, copy paste and slightly modify the machine configur

#yocto

Hi Bhavya, SRC_URI = "file://gsm-${PV}.tar.gz \ file://license" or SRC_URI = "file://gsm-${PV}.tar.gz" SRC_URI += "file://license" Quentin

#yocto

Hi Bhavya, Your S = "${WORKDIR}" is probably wrong then. Is there only a directory "at the root" of the tarball? I mean if you untar it, do you get one directory where all your source code is? In that

#yocto

Hi, Don't know if it works but was always wondering if adding PACKAGE_EXCLUDE = "connman" would be a way to know for sure at least one recipe that is "adding" connman to the image exists (and this als

Hi Robm For location of bbappends and recipes, etc.: bitbake-layers show-appends bitbake-layers show-recipes For variables: bitbake <recipe> -e | more and find the line starting with the variable you'

Hi Sheng Leong, Start from a core-image-minimal and add packages manually. Only the packages that are specified to be installed explicitly in your image recipe and the packages specified in RDEPENDS a

#linux #yocto #cups #hplip

Hi Lluis, It's known: https://twitter.com/yoctoproject/status/1290570140468285441?s=20 Thanks for the report anyway :) Quentin

Hi Itai, SDKTARGETSYSROOT = "${STAGING_BINDIR_NATIVE}/mips64-poky-linux" --sysroot=${STAGING_DIR_TARGET} \ --sysroot=${STAGING_DIR_TARGET} --sysroot=${STAGING_DIR_TARGET} -L/${STAGING_LIBDIR} At least

Hi Rob, DEPENDS_${PN} does nothing, so that's not what fixed it ;) I doubt LOCAL_VERSION_EXTEND or however it's called is used for creating the package version of the kernel. I'd expect the dependenci

Hi Sergey, No need. No need. No need, default is the name of the recipe file. No need, default is the version in the recipe file (if there's one). meta-ice_layer/recipes-ice/ice_helloworld/ice_hellowo

Hi Sergey, DEPENDS = "util-linux" (DEPENDS is for build time dependencies and you add the recipe providing the sources for it, RDEPENDS_${PN} is for runtime dependencies and you add packages to it (it

Hi

Hi Greg, .so files are installed in the -dev package even with the line above. Please have a look here: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libr

Hi Talel, RDEPENDS is for runtime dependencies, DEPENDS is for build time, so you want to use DEPENDS here. Cheers, Quentin

#yocto

Hi Talel, Use devtool finish when you're done with a recipe you started with devtool add, that should do it. Quentin

If your recipe is in: /media/talel/data/multigate/multigate/meta-wirepas/recipes-wirepas/wirepas-gateway/ and wp-gateway.zip is in: /media/talel/data/multigate/multigate/meta-wirepas/recipes-wirepas/w

If available in krogoth, `oe-pkdata-util find-path /etc/network/if-up,d/hostapd_restart` does this exact thing :) Quentin

Hi Steve, It comes with systemd. Use it as your init system and then you'll have the command. Quentin

#systemd #yocto #linux

Hi Talel, Just guessing but probably nodejs-native here? Although, you might want to have a look at the npm.bbclass and try to inherit it. Considering how complex the class looks like, it might be eas