Using Devtool to Streamline Your Yocto Project Workflow - Tim Orling, Intel

The Linux Foundation · 15K views · 2017 · 48:32

Open on YouTube

Linux & open-source ecosystemsTesting, debugging & developer toolsSoftware (other)talkdated

Why Stack Overflow recommends it

Stack Overflow users link it when answering or asking about how to create Yocto recipes and use devtool commands like add, build, deploy-target and finish.

Recommended by 1 people across 2 different months, 2017 to 2018.

What it is

A 48-minute Embedded Linux Conference talk by Tim Orling of Intel on devtool, the Yocto Project tool for creating, modifying and deploying packages built by the OpenEmbedded system. It covers how devtool has improved since Yocto 1.8, its current capabilities, and planned features, including a walkthrough of adding, building and deploying a package to a target.

What people said

Recommends Nayfe · 2017-11 · Stack Overflow · on “trying to create squidguard recipe in oe-core”

Correct syntax is `LIC_FILES_CHKSUM = " \ file://COPYING;md5=17cccb55725bad30d60ee344fa9561e \ "` I suggest you to look at devtool to create recipes, this video is really instructive [this video]

Recommends Nayfe · 2018-03 · Stack Overflow · on “Building packages to yocto image (image) without using recipes”

Nop, there is no support for Debian packages. If you want to add tensorflow to Yocto image, you'll need to create a recipe for it. You can look at this video [this video] . For numpy and pyserial, you can it with following statement in local.conf: `IMAGE_INSTALL_append = " python3-numpy python3-pyserial "`. I can't see any tensorflow nor h5py existing recipes.

Recommends Nayfe · 2018-03 · Stack Overflow · on “Building packages to yocto image (image) without using recipes”

Did you look at this video on devtool [this video] ? It is the recommanded way to create recipes, to support new packages. Buildroot [LINK] is an alternative to Yocto. By the way, what is your target machine? You can also join #Yocto channel on irc [LINK] .

Cites KostaZ · 2018-03 · Stack Overflow · on “What's the difference between 'devtool build-image <image>' and 'bitbake <image>'?”

I'm working with rocko branch. I use the regular way to build an image via: bitbake core-image-full-cmdline All works fine! Now, I'm trying to work with devtool [this video] and then I need to use another way to build the core image: devtool build-image core-image-full-cmdline So, what's the difference between devtool build-image <image> and bitbake <image> ?

Cites user4851126 · 2018-05 · Stack Overflow · on “Include an Application Image in Yocto Build”

I believe it gets a bit complicated in Yocto: You need to create your own layer [LINK] . Let's say meta-hello . This folder needs to in the same place as all your other meta layers and also where your poky directory is. You need to enable that layer in your bblayers.conf file. For that you can use bitbake-layers add-layer /path/to/meta-hello Now within your meta-hello create a recipe in a folder recipes-hello/hello your hello.bb file is within the above mentioned folder and your can decide to use either automake , makefile or compile it accordingly using the Dev Manual Here [LINK] Once that is done, in your BUILD dir perform bitbake hello and this will compile and provide errors if any. Reso

Cites user4851126 · 2018-05 · Stack Overflow · on “In devtool command line tool is finish subcommand removed or replaced?”

The only relevant and easy to understand example I found to use devtool in a Yocto Workflow was the Video from Tim Orling in Embedded Linux Conference [this video] In his workflow: He uses devtool add to add nano devtool build to build it devtool deploy-target to deploy it on qemu devtool undeploy-target to remove nano devtool finish nano ../meta-foo I tried doing the same thing but there is no subcommand finish in devtool when I try devtool finish --help devtool finish --help ERROR: argument <subcommand>: invalid choice: 'finish' (choose from 'create-workspace', 'add', 'modify', 'extract', 'sync', 'update-recipe', 'status', 'reset', 'build-image', 'deploy-target', 'undeploy-target', 'build', 'se