[yocto] Yocto eSDK, Editing/Adding Recipes, and VCS

Paul Eggleton paul.eggleton at linux.intel.com
Wed Jun 21 02:27:20 PDT 2017

Hi Aaron,

On Tuesday, 20 June 2017 11:04:56 PM CEST Aaron_Wright at selinc.com wrote:
> I've been trying to document some workflows for my developers using the 
> Yocto eSDK for our image, but I am coming up empty when it comes to 
> editing or adding recipes. I can use devtool to edit a recipe like so:
> devtool edit-recipe -a my-recipe
> But any changes I make are hidden away in the 
> esdk/layers/poky/meta-mylayer directory, which isn't managed by a VCS (git 
> in this instance). So there's this modified file in a directory--great. 
> What is the developer supposed to do with it? Copy it over to a VCS 
> managed directory of meta-mylayer, commit, and push?
> I feel like I'm missing something with the devtool workflow. Can anyone 
> point me in the right direction?

So making changes to existing recipes isn't a very well developed area of the
eSDK at the moment, you're not missing anything. There is a bug open to deal
with this:


Thinking off the top of my head, a relatively simple workaround would be
to do something like this (in your image recipe or a class inherited from

sdk_ext_postinst_append() {
	cd $target_sdk_dir/layers/<layerpath>
	git init
	git add -A .
	git commit -m "Initial commit"
	cd $target_sdk_dir

This will be executed at the end of installation and would at least let you track
changes, although as you rightly point out they will be a bit buried inside the
SDK structure.



Paul Eggleton
Intel Open Source Technology Centre

More information about the yocto mailing list