Application Development with Extensible SDK - Revision history

Matt Hansen: /* Create a recipe from existing source */

2017-06-23T18:26:21Z

Create a recipe from existing source

← Older revision		Revision as of 18:26, 23 June 2017
Line 42:		Line 42:
	== Create a recipe from existing source ==		== Create a recipe from existing source ==
	Before generating your recipe, it's best to build the base image first, then you will only have to build your application after adding the recipe. This can be done using devtool:		Before generating your recipe, it's best to build the base image first, then you will only have to build your application after adding the recipe. This can be done using devtool:
	devtool build-image ~~core-image-full-cmdline~~		devtool build-image

	=== Generate recipe ===		=== Generate recipe ===

Matt Hansen: /* Create a recipe from existing source */

2017-06-23T18:13:06Z

Create a recipe from existing source

← Older revision		Revision as of 18:13, 23 June 2017
Line 42:		Line 42:
	== Create a recipe from existing source ==		== Create a recipe from existing source ==
	Before generating your recipe, it's best to build the base image first, then you will only have to build your application after adding the recipe. This can be done using devtool:		Before generating your recipe, it's best to build the base image first, then you will only have to build your application after adding the recipe. This can be done using devtool:
	devtool build-image [image-~~name]~~		devtool build-image core-image-full-cmdline

	=== Generate recipe ===		=== Generate recipe ===

Matt Hansen: /* Create a recipe from existing source */

2017-06-23T18:07:52Z

Create a recipe from existing source

← Older revision		Revision as of 18:07, 23 June 2017
Line 41:		Line 41:

	== Create a recipe from existing source ==		== Create a recipe from existing source ==
			Before generating your recipe, it's best to build the base image first, then you will only have to build your application after adding the recipe. This can be done using devtool:
			devtool build-image [image-name]

	=== Generate recipe ===		=== Generate recipe ===
	Let's say you have a C application that you want to add to your OS image. Assume repo is https://github.com/whbruce/bbexample.git and you want to name recipe (and thus the executable it creates) bbexample. The best way of doing this is use [http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#dev-modifying-source-code '''devtool''']		Let's say you have a C application that you want to add to your OS image. Assume repo is https://github.com/whbruce/bbexample.git and you want to name recipe (and thus the executable it creates) bbexample. The best way of doing this is use [http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#dev-modifying-source-code '''devtool''']

Henry Bruce: /* Publish */

2017-04-08T00:28:38Z

Publish

← Older revision		Revision as of 00:28, 8 April 2017
Line 127:		Line 127:

	=== Publish ===		=== Publish ===
	~~The <tt>devtool publish</tt> command first appeared in Yocto 2.2.~~
	~~==== Publish with Yocto 2.2 and later ====~~
	Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, accept all default values. The bitbake-layers script will add the later to BBLAYERS.		Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, accept all default values. The bitbake-layers script will add the later to BBLAYERS.
	$ layers/poky/scripts/yocto-layer create /path/to/meta-example		$ layers/poky/scripts/yocto-layer create /path/to/meta-example
	$ layers/poky/bitbake/bin/bitbake-layers add-layer /path/to/meta-example		$ layers/poky/bitbake/bin/bitbake-layers add-layer /path/to/meta-example
	Now we move over the recipe we created, along with the patch for the source code.		Now we move over the recipe we created, along with the patch for the source code. The <tt>devtool publish</tt> command first appeared in Yocto 2.2 which grearly simplifies this task.
			==== Yocto 2.2 and later ====
	$ devtool finish bbexample meta-example		$ devtool finish bbexample meta-example
	This will create a recipes folder called recipes-bbexample, with a recipe called bbexample_git.bb in it. You should change the recipe name to reflect the version (e.g. bbexample_0.1.bb)		This will create a recipes folder called recipes-bbexample, with a recipe called bbexample_git.bb in it. You should change the recipe name to reflect the version (e.g. bbexample_0.1.bb)
	==== ~~Publish with~~ Yocto 2.1 ~~and ealier~~ ====		==== Yocto 2.1 ====
			Manually create patches then copy over recipe and patches. More details to come.

	== Update Existing Recipe ==		== Update Existing Recipe ==

Henry Bruce: /* Publish */

2017-04-08T00:25:00Z

Publish

← Older revision		Revision as of 00:25, 8 April 2017
Line 127:		Line 127:

	=== Publish ===		=== Publish ===
			The <tt>devtool publish</tt> command first appeared in Yocto 2.2.
			==== Publish with Yocto 2.2 and later ====
	Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, accept all default values. The bitbake-layers script will add the later to BBLAYERS.		Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, accept all default values. The bitbake-layers script will add the later to BBLAYERS.
	$ layers/poky/scripts/yocto-layer create /path/to/meta-example		$ layers/poky/scripts/yocto-layer create /path/to/meta-example
Line 133:		Line 135:
	$ devtool finish bbexample meta-example		$ devtool finish bbexample meta-example
	This will create a recipes folder called recipes-bbexample, with a recipe called bbexample_git.bb in it. You should change the recipe name to reflect the version (e.g. bbexample_0.1.bb)		This will create a recipes folder called recipes-bbexample, with a recipe called bbexample_git.bb in it. You should change the recipe name to reflect the version (e.g. bbexample_0.1.bb)
			==== Publish with Yocto 2.1 and ealier ====

	== Update Existing Recipe ==		== Update Existing Recipe ==

Henry Bruce: /* What devtool can do */

2016-12-14T19:39:12Z

What devtool can do

← Older revision		Revision as of 19:39, 14 December 2016
Line 14:		Line 14:
	* To integrate that change into the rest of the OpenEmbedded (OE) build system.		* To integrate that change into the rest of the OpenEmbedded (OE) build system.

	In short, we can think of devtool as a single point of entry for creating, modifying and testing recipes.		In short, we can think of devtool as a single point of entry for creating, modifying and testing recipes. Read this section of the [http://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-a-closer-look-at-devtool-add SDK manual] to find out more on the types of projects devtool can support].

	=== What devtool cannot do ===		=== What devtool cannot do ===

Henry Bruce: /* Publish */

2016-10-24T23:28:33Z

Publish

← Older revision		Revision as of 23:28, 24 October 2016
Line 127:		Line 127:

	=== Publish ===		=== Publish ===
	Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, ~~acceplt~~ all default values. The bitbake-layers ~~scriopt~~ will add the later to BBLAYERS.		Now you'll want to add your new app to a layer. In this example, we'll create a new layer called meta-example in folder /path/to, but an existing layer can also be used. First create the layer and it add it BBLAYERS. We use the yocto-layer utility. When you run it, accept all default values. The bitbake-layers script will add the later to BBLAYERS.
	$ layers/poky/scripts/yocto-layer create /path/to/meta-example		$ layers/poky/scripts/yocto-layer create /path/to/meta-example
	$ ~~layer~~/poky/~~scripts~~/bitbake-layers add-layer /path/to/meta-example		$ layers/poky/bitbake/bin/bitbake-layers add-layer /path/to/meta-example
	Now we move over the recipe we created, along with the patch for the source code.		Now we move over the recipe we created, along with the patch for the source code.
	$ devtool finish bbexample meta-example		$ devtool finish bbexample meta-example

Henry Bruce at 23:11, 24 October 2016

2016-10-24T23:11:13Z

← Older revision		Revision as of 23:11, 24 October 2016
Line 1:		Line 1:
	'''[WORK IN PROGRESS]'''		'''[WORK IN PROGRESS].''' Back to the [[Cookbook]] home page.
	== Introduction ==		== Introduction ==
	Welcome to the Yocto Project Test Kitchen! It can be a bit overwhelming to know where to start with the Yocto Project. You know you want to build an application that runs on embedded hardware, but where and how do you get started? A development environment can be an abstract, somewhat hard-to-imagine thing. This part of the wiki is intended to fill the knowledge gap between the [http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html Quick Start] and the myriad of ways to build an image and run it on real (or emulated) hardware. So what better way to do that than with a "Test Kitchen" analogy?		Welcome to the Yocto Project Test Kitchen! It can be a bit overwhelming to know where to start with the Yocto Project. You know you want to build an application that runs on embedded hardware, but where and how do you get started? A development environment can be an abstract, somewhat hard-to-imagine thing. This part of the wiki is intended to fill the knowledge gap between the [http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html Quick Start] and the myriad of ways to build an image and run it on real (or emulated) hardware. So what better way to do that than with a "Test Kitchen" analogy?
Line 174:		Line 174:
	NOTE: Successfully built core-image-minimal. You can find output files in /path/to/build/tmp/deploy/images/qemux86		NOTE: Successfully built core-image-minimal. You can find output files in /path/to/build/tmp/deploy/images/qemux86
	</pre>		</pre>


	~~'''[WORK IN PROGRESS]'''~~

	~~<hr>~~
	~~Back to the [[Cookbook]] home page.~~

Henry Bruce: /* Update */

2016-10-24T23:10:06Z

Update

← Older revision		Revision as of 23:10, 24 October 2016
Line 124:		Line 124:
	Now the application is packaged, you'll probably want to make some changes. This examples assumes that you cannot push you changes upstream so have to apply them as a patch. Let's simply update the app to output		Now the application is packaged, you'll probably want to make some changes. This examples assumes that you cannot push you changes upstream so have to apply them as a patch. Let's simply update the app to output
	Hello Yocto World v2...		Hello Yocto World v2...
	Make the change to bbexample.c and commit with message "Changed bbexample message" and check that bbexample operates as expected.		Make the change to bbexample.c and commit with message "Changed bbexample message" and check that bbexample operates as expected. Note that if you are using devtool from the eSDK it will create temporary folders <tt>oe-logs</tt> and <tt>oe-workdir</tt> so you should configure git to ignore them.

	=== Publish ===		=== Publish ===

Henry Bruce: /* Update Existing Recipe */

2016-10-24T23:07:05Z

Update Existing Recipe

← Older revision		Revision as of 23:07, 24 October 2016
Line 135:		Line 135:

	== Update Existing Recipe ==		== Update Existing Recipe ==
	Updating a recipe is similar to creating one; however, rather than using <tt>devtool add</tt> we use the <tt>devtool modify</tt> command.		Updating a recipe is similar to creating one; however, rather than using <tt>devtool add</tt> we use the <tt>devtool modify</tt> command.
	devtool modify bbexample		devtool modify bbexample
			The edit/build/test cycle is then the same as for adding a recipe but note that the recipe is not copied into devtool's workspace but remains in its layer.
	The edit/build/test cycle is then the same as for adding a recipe.

	== Build Image ==		== Build Image ==