Using devtool in Yocto to patch/customize recipe/package sources

-
When you build a particular recipe by running the command "bitbake <recipe_name>", yocto framework creates a tmp/work/<architecture>/<recipe>/<version> directory. Also known as "work" directory. This is the directory where Yocto performs all the tasks such as fetching the source, configuring, building and packaging etc.

Sometimes, you need to add customizations on top of downloaded recipe source code.
For example you have 'matchbox-terminal' recipe and you have a customization to hide the title bar.

You will find the work directory in 'build/tmp/work/corei7-64-poky-linux/matchbox-terminal/0.1-r0/' and source code in 'build/tmp/work/corei7-64-poky-linux/matchbox-terminal/0.1-r0/git/'



To add our customizations, we basically open main.c and add our customizations and then recompile it using bitbake command, and this is not the best approach in Yocto for making customizations, as  you can easily lose the changes


Yocto provides a tool/utility 'devtool' which allows you to make changes in the source code of a particular recipe, it creates a patch as well as bbappend file for us.

Steps to use devtool for customization:

1. Run 'devtool modify <recipename>' command, in our case it is 'devtool modify matchbox-terminal' . This command will fetch the sources and unpack them in 'build/workspace/sources/<recipename> directory.

2. Make the required changes in your source code

3. Build the recipe using 'bitbake <recipename>' to verify/test your changes
4. Once you are happy with the changes, you go to the source folder and commit your changes

5. Now run 'devtool update-recipe <recipename> -a <path to your layer>' command which will create a bbappend and patch of changes you made

6. Finally, you can delete the build/workspace/sources/<recipename> folder

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more