Hi, No target named install. Add one or override do_install task since by default it "calls" the install target. [...] IIRC, gitsm in SRC_URI instead of git should handle that: https://docs.yoctoproje

#yocto #toolchain #linux

Hi Andrew, OVERRIDES is set in configuration files usually (always?). It can be either in a distro if you use DISTROOVERRIDES, in a machine if you use MACHINEOVERRIDES, and you might be able to add ma

Hi VR, You need to put the SDK filename into SRC_URI as well otherwise Yocto does not fetch it from the files directory. Also, Ross had a good suggestion too, please check that the recipe or a similar

#dunfell #linux #yocto

Hi VR, If you don't give us the log, we won't be able to help you. Where is the sdk? You need to add it into your SRC_URI (you can also just pass a URL to a git repo or tarball download link). Quentin

#dunfell #linux #yocto

Hi, To be able to help you we'd need the logs of this task. You can either paste the whole output on the console or send us the task log you can find if you carefully read the console output. Quentin

Hi Michael, Use an anonymous python function that sets VERSION, e.g.: python __anonymous() { d.setVar('VERSION', find_version(d)) } as anonymous python functions are always executed during parsing. Th

Hi, You're not compiling a package, you're compiling a recipe named obexpushtest whose output is packages (one of which is named the same as the recipe, hence the confusion). But here, you're adding a

Hi, You're not compiling a package, you're compiling a recipe named obexpushtest whose output is packages (one of which is named the same as the recipe, hence the confusion). But here, you're adding a

Hi, I gave you what you have to do in the previous mail. Remove the last two lines of your bb file. If it does not work, give the full error logs and what you're trying to achieve and what you have. Q

Hi, You're not compiling a package, you're compiling a recipe named obexpushtest whose output is packages (one of which is named the same as the recipe, hence the confusion). But here, you're adding a

Hi Talel, SRC_URI_append_mezu-media = " file://media.patch" is what you should use. The issue with your suggestion is that it **replaces** the original variable iff the recipe is built for menzu-media

Hi Talel, If the native version of python3-cffi is needed, add DEPENDS = "python3-cffi-native". Quentin

Hi Byron, Did you execute the commands that were suggested in the log you sent? Can you send us the content of the log of the second command please? Basically, two possible ways this happens: 1. you m

It is, you just answered the wrong mail so my answer isn't in the body of this mail. You don't need to change anything in the networkmanager recipe. You need to add networkmanager-nmcli to the package

#nmcli #yocto

Please keep the mailing list in copy so everyone can benefit from your progress/the solution, thanks! This is an option at build time (i.e. for the **recipe**). It just configures the piece of SW you'

#yocto #nmcli

Hi, You need to bitbake networkmanager but install networkmanager-nmcli and/or networkmanager-nmtui, c.f. http://cgit.openembedded.org/meta-openembedded/tree/meta-networking/recipes-connectivity/netwo

#nmcli #yocto

Hi Robert, I'd say they either should be added to IMAGE_INSTALL one by one, or being put into a packagegroup or even use RRECOMMENDS instead of RDEPENDS. To me, it feels wrong too, if it's really not

Hi Steve, You have a few of the changes highlighted in: https://docs.yoctoproject.org/ref-manual/migration.html Obviously, you'd need to do all the changes between Rocko and the version you're targett

#yocto

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

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

#systemd #yocto #linux