Using devtool to modify recipes in Yocto - Revision history

Koan: /* Using devtool to modify recipes in Yocto */

2024-03-05T16:16:03Z

Using devtool to modify recipes in Yocto

← Older revision		Revision as of 16:16, 5 March 2024
Line 18:		Line 18:
	# Run <code>devtool modify <recipename></code>. This will fetch the sources for the recipe and unpack them to a workspace/sources/<recipename> directory and initialise it as a git repository if it isn't already one. If you prefer you can specify your own path, or if you already have your own existing source tree you can specify the path along with the -n option to use that instead of unpacking a new one.		# Run <code>devtool modify <recipename></code>. This will fetch the sources for the recipe and unpack them to a workspace/sources/<recipename> directory and initialise it as a git repository if it isn't already one. If you prefer you can specify your own path, or if you already have your own existing source tree you can specify the path along with the -n option to use that instead of unpacking a new one.
	# Make the changes you want to make to the source		# Make the changes you want to make to the source
	# Run a build to test your changes - you can just <code>~~bitbake~~ <recipename></code> or even build an entire image incorporating the changes assuming a package produced by the recipe is part of an image. There's no need to force anything - the build system will detect changes to the source and recompile as necessary.		# Run a build to test your changes - you can just <code>devtool build <recipename></code> or even build an entire image incorporating the changes assuming a package produced by the recipe is part of an image. There's no need to force anything - the build system will detect changes to the source and recompile as necessary.
	# If you wish, test your changes on the target. There's a "devtool deploy-target" command which will copy the files installed at do_install over to the target machine assuming it has network access, and any dependencies are already present in the image.		# If you wish, test your changes on the target. There's a "devtool deploy-target" command which will copy the files installed at do_install over to the target machine assuming it has network access, and any dependencies are already present in the image.
	# Repeat from step 2 as needed until you're happy with the results.		# Repeat from step 2 as needed until you're happy with the results.

Koan: /* Using devtool to modify the linux kernel configuration */

2020-12-17T13:24:04Z

Using devtool to modify the linux kernel configuration

← Older revision		Revision as of 13:24, 17 December 2020
Line 70:		Line 70:

	== Using devtool to modify the linux kernel configuration ==		== Using devtool to modify the linux kernel configuration ==

			'''WARNING: the <code>devtool menuconfig</code> option is valid only for recent Yocto releases like '''dunfell''' '''

	Modifying the kernel configuration may be different depending on the original conditions		Modifying the kernel configuration may be different depending on the original conditions

Koan at 16:28, 30 November 2020

2020-11-30T16:28:12Z

← Older revision		Revision as of 16:28, 30 November 2020
Line 65:		Line 65:

	git add .		git add .


	git commit -m "my linux modifications"		git commit -m "my linux modifications"
	devtool update-recipe linux-yocto		devtool update-recipe linux-yocto

	~~<br />~~

Koan at 16:27, 30 November 2020

2020-11-30T16:27:49Z

@@ Line 38: / Line 38: @@
 Modifying the kernel inside Yocto/OE
-# From your build directory run
+From your build directory run
   devtool modify virtual/kernel
@@ Line 65: / Line 65: @@
   git add .
   git commit -m "my linux modifications"
   devtool update-recipe linux-yocto
 <br />

Koan at 16:21, 30 November 2020

2020-11-30T16:21:13Z

@@ Line 1: / Line 1: @@
-== Creating Using devtool to modify recipes in Yocto ==
+== Using devtool to modify recipes in Yocto ==
 Suppose you have a requirement of customizing an existing sources for a recipe, <code>devtool</code> will be the best option to go, as it will do all the steps required to create a patch, <code>bbappend</code> file etc.
-As part of building a recipe, Yocto/OE creates a tmp/work/<architecture>/<recipe>/<version> directory, known as the "work directory".
+As part of building a recipe, Yocto/OE creates a <code>tmp/work/<architecture>/<recipe>/<version></code> directory, known as the "work directory". <br /><br />
-This is where all of the work done to build a recipe takes place.
+This is where all of the work done to build a recipe takes place. <br /><br />
-One of the things you'll find in this directory is the source, usually under a subdirectory named <recipename>-<version> or "git" (depending on how the fetched source is provided).
+One of the things you'll find in this directory is the source, usually under a subdirectory named <code><recipename>-<version></code> or "git" (depending on how the fetched source is provided). <br /><br />
 The temptation (and what people used to do in the past) is to simply make changes here and then recompile, but there are several reasons why that's not a good idea:
 * It's awkward - you have to use <code>bitbake -c compile -f</code> or <code>bitbake -C compile</code> to force recompilation, since the build system doesn't know that you've made any changes
 * You can easily lose your changes if you're not careful e.g. running <code>bitbake -c clean</code> will wipe the directory out
 Luckily there's a much better method using the <code>devtool</code> command:

Koan at 16:08, 30 November 2020

2020-11-30T16:08:18Z

← Older revision		Revision as of 16:08, 30 November 2020
Line 1:		Line 1:
	== Creating Using devtool to modify recipes in Yocto ==		== Creating Using devtool to modify recipes in Yocto ==

	Suppose you have a requirement of customizing an existing sources for a recipe, <code>devtool</code> will be the best option to go, as it will do all the steps required to create a patch, bbappend file etc.		Suppose you have a requirement of customizing an existing sources for a recipe, <code>devtool</code> will be the best option to go, as it will do all the steps required to create a patch, <code>bbappend</code> file etc.

			As part of building a recipe, Yocto/OE creates a tmp/work/<architecture>/<recipe>/<version> directory, known as the "work directory".
			This is where all of the work done to build a recipe takes place.
			One of the things you'll find in this directory is the source, usually under a subdirectory named <recipename>-<version> or "git" (depending on how the fetched source is provided).
			The temptation (and what people used to do in the past) is to simply make changes here and then recompile, but there are several reasons why that's not a good idea:

			* It's awkward - you have to use <code>bitbake -c compile -f</code> or <code>bitbake -C compile</code> to force recompilation, since the build system doesn't know that you've made any changes
			* You can easily lose your changes if you're not careful e.g. running <code>bitbake -c clean</code> will wipe the directory out

			Luckily there's a much better method using the <code>devtool</code> command:

Koan: Created page with "== Creating Using devtool to modify recipes in Yocto == Suppose you have a requirement of customizing an existing sources for a recipe, `devtool` will be the best..."

2020-11-30T16:06:39Z

Created page with "== Creating Using devtool to modify recipes in Yocto == Suppose you have a requirement of customizing an existing sources for a recipe, <code>devtool</code> will be the best..."

New page

== Creating Using devtool to modify recipes in Yocto ==

Suppose you have a requirement of customizing an existing sources for a recipe, <code>devtool</code> will be the best option to go, as it will do all the steps required to create a patch, bbappend file etc.