Application Development with Legacy SDK - Revision history

L.S. Cook: L.S. Cook moved page Application Development to Application Development with Legacy SDK

2016-08-26T18:31:21Z

L.S. Cook moved page Application Development to Application Development with Legacy SDK

← Older revision	Revision as of 18:31, 26 August 2016
(No difference)

L.S. Cook at 18:30, 26 August 2016

2016-08-26T18:30:46Z

← Older revision		Revision as of 18:30, 26 August 2016
Line 4:		Line 4:


	== Application Development ==		== Application Development with Legacy SDK==

	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?

L.S. Cook at 18:18, 22 August 2016

2016-08-22T18:18:47Z

← Older revision		Revision as of 18:18, 22 August 2016
Line 26:		Line 26:
	===Process===		===Process===

	Use these steps to set up your SDK dev environment ~~as a~~ QEMU emulator.		Use these steps to set up your SDK dev environment with QEMU (emulator).

	1. Locate and download QEMU-compatible images from the latest Yocto releases from http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/machines/qemu/qemux86-64		1. Locate and download QEMU-compatible images from the latest Yocto releases from http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/machines/qemu/qemux86-64

L.S. Cook at 14:37, 9 August 2016

2016-08-09T14:37:47Z

← Older revision		Revision as of 14:37, 9 August 2016
Line 6:		Line 6:
	== Application Development ==		== Application Development ==

	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?

	Our Test Kitchen must be Linux-powered, of course. And using one of the [http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#detailed-supported-distros supported distributions] in our Linux-powered kitchen means that we'll already either '''have''' or have a way to '''easily get''' everything we need to follow the recipes in our Cookbook.		Our Test Kitchen must be Linux-powered, of course. And using one of the [http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#detailed-supported-distros supported distributions] in our Linux-powered kitchen means that we'll already either '''have''' or have a way to '''easily get''' everything we need to follow the recipes in our Cookbook.
Line 232:		Line 232:
	NOTE: Updating recipe mdadm_3.4.bb		NOTE: Updating recipe mdadm_3.4.bb

	~~The patch is~~ located here:		which will be located here:

	$HOME/poky_sdk/layers/build/meta/recipes-extended/mdadm/mdadm/0001-ReadMe.c-Updated-the-version-string.patch		$HOME/poky_sdk/layers/build/meta/recipes-extended/mdadm/mdadm/0001-ReadMe.c-Updated-the-version-string.patch

L.S. Cook: /* Modifying Existing Functionality */

2016-08-09T13:53:21Z

Modifying Existing Functionality

← Older revision		Revision as of 13:53, 9 August 2016
Line 166:		Line 166:
	==== Modifying Existing Functionality ====		==== Modifying Existing Functionality ====

	Another common scenario is to modify code that already has an existing recipe in place. This is different ~~that~~ adding brand new functionality as was demonstrated in the previous section.		Another common scenario is to modify code that already has an existing recipe in place. This is different from adding brand new functionality, as was demonstrated in the previous section.

	To help demonstrate this concept, we will use a more ~~“real~~-~~world”~~ example: the existing multiple device administrator (<code>mdadm</code>) module, which is a core module included as part of the installed Yocto Project SDK. The steps in this section will modify <code>mdadm</code> to change the reported version, which is 3.4.		To help demonstrate this concept, we will use a more "real-world" example: the existing multiple device administrator (<code>mdadm</code>) module, which is a core module included as part of the installed Yocto Project SDK. The steps in this section will modify <code>mdadm</code> to change the reported version, which is 3.4.

	Follow these steps to modify <code>mdadm</code>		Follow these steps to modify <code>mdadm</code>:

	1. Run <code>devtool modify</code> to locate, extract, and prepare all of the <code>mdadm</code> files. This command locates the source based on information in the existing recipe, unpacks the source into your workspace, applies any existing patches, and parses all related recipes:		1. Run <code>devtool modify</code> to locate, extract, and prepare all of the <code>mdadm</code> files. This command locates the source based on information in the existing recipe, unpacks the source into your workspace, applies any existing patches, and parses all related recipes:

L.S. Cook at 20:22, 8 August 2016

2016-08-08T20:22:46Z

← Older revision		Revision as of 20:22, 8 August 2016
Line 1:		Line 1:
			Back to Yocto Project [[Cookbook]]

	[ Work In Process ]		This section is currently a [ '''Work In Process''' ]

L.S. Cook: /* Modifying Existing Functionality */

2016-08-08T14:57:31Z

Modifying Existing Functionality

← Older revision		Revision as of 14:57, 8 August 2016
Line 208:		Line 208:

	sh-4.3# mdadm -V		sh-4.3# mdadm -V
	mdadm - v 3.~~4-modified~~ 21 June 2016		mdadm - v 3.4a 21 June 2016
	sh-4.3#		sh-4.3#

Line 221:		Line 221:

	$ git add ReadMe.c		$ git add ReadMe.c
	$ git commit -m 'ReadMe.c-Updated-the-version-string'		$ git commit -m "ReadMe.c-Updated-the-version-string"

	7. Turn the commit you have made into a patch:		7. Turn the commit you have made into a patch:

L.S. Cook: /* Process */

2016-08-08T14:55:02Z

Process

← Older revision		Revision as of 14:55, 8 August 2016
Line 74:		Line 74:
	The <code>helloworld/hello.c</code> file is as follows:		The <code>helloworld/hello.c</code> file is as follows:

			<pre>
	#include <stdio.h>		#include <stdio.h>

	main()		main()
	{		{
	printf("Hello World!\n");		printf("Hello World:\n");
	}		}
			</pre>

	The <code>helloworld/Makefile.am</code> file is as follows:		The <code>helloworld/Makefile.am</code> file is as follows:

L.S. Cook: /* Process */

2016-08-08T14:52:26Z

Process

← Older revision		Revision as of 14:52, 8 August 2016
Line 182:		Line 182:
	NOTE: Recipe mdadm now set up to build from /home/username/poky_sdk/workspace/sources/mdadm.		NOTE: Recipe mdadm now set up to build from /home/username/poky_sdk/workspace/sources/mdadm.

	2. In the source location <code>$HOME/poky_sdk/workspace/sources/mdadm</code>, use an editor to edit the <code>~~README~~.C</code> file. Change the line that specifies the version as '''3.4''' to say '''3.4a'''.		2. In the source location <code>$HOME/poky_sdk/workspace/sources/mdadm</code>, use an editor to edit the <code>Readme.c</code> file. Change the line that specifies the version as '''3.4''' to say '''3.4a'''.

	#define VERSION "3.4a"		#define VERSION "3.4a"
Line 202:		Line 202:
	$ devtool deploy-target mdadm root@192.168.7.2		$ devtool deploy-target mdadm root@192.168.7.2
	NOTE: Successfully deployed /home/username/poky_sdk/tmp/work/core2-64-poky-linux/mdadm/3.4-r0/image		NOTE: Successfully deployed /home/username/poky_sdk/tmp/work/core2-64-poky-linux/mdadm/3.4-r0/image
	5. In the shell running QEMU, verify your changes by running ~~“mdadm”~~ and providing the “-V” option to return the version:

			5. In the shell running QEMU, verify your changes by running <code>mdadm</code> and providing the <code>-V</code> option to return the version:

	sh-4.3# mdadm -V		sh-4.3# mdadm -V
Line 208:		Line 210:
	sh-4.3#		sh-4.3#

	'''NOTE''': If you try to use the previous command to see the original version of <code>mdadm</code>, you will get a message indicating the command is not found; <code>mdadm</code. is not in the image by default.		'''NOTE''': If you try to use the previous command to see the original version of <code>mdadm</code>, you will get a message indicating the command is not found; <code>mdadm</code>. is not in the image by default.

	6. At this point, you have modified the source code of an existing module all within your workspace. If you want to save your work, commit those changes. You can use the following commands to see the changes that need to be staged and committed:		6. At this point, you have modified the source code of an existing module all within your workspace. If you want to save your work, commit those changes. You can use the following commands to see the changes that need to be staged and committed:

L.S. Cook at 14:49, 8 August 2016

2016-08-08T14:49:49Z

← Older revision		Revision as of 14:49, 8 August 2016
Line 158:		Line 158:

	$HOME/poky_sdk/workspace/recipes/helloworld		$HOME/poky_sdk/workspace/recipes/helloworld




			==== Modifying Existing Functionality ====

			Another common scenario is to modify code that already has an existing recipe in place. This is different that adding brand new functionality as was demonstrated in the previous section.

			To help demonstrate this concept, we will use a more “real-world” example: the existing multiple device administrator (<code>mdadm</code>) module, which is a core module included as part of the installed Yocto Project SDK. The steps in this section will modify <code>mdadm</code> to change the reported version, which is 3.4.

			Follow these steps to modify <code>mdadm</code>

			1. Run <code>devtool modify</code> to locate, extract, and prepare all of the <code>mdadm</code> files. This command locates the source based on information in the existing recipe, unpacks the source into your workspace, applies any existing patches, and parses all related recipes:

			$ devtool modify mdadm
			Parsing recipes..done.
			NOTE: Fetching mdadm…
			NOTE: Unpacking…
			NOTE: Patching…
			NOTE: Adding local source files to srctree…
			NOTE: Source tree extracted to /home/username/poky_sdk/workspace/sources/mdadm
			NOTE: Using source tree as build directory since recipe inherits autotools-brokensep
			NOTE: Recipe mdadm now set up to build from /home/username/poky_sdk/workspace/sources/mdadm.

			2. In the source location <code>$HOME/poky_sdk/workspace/sources/mdadm</code>, use an editor to edit the <code>README.C</code> file. Change the line that specifies the version as '''3.4''' to say '''3.4a'''.

			#define VERSION "3.4a"

			3. Rebuild <code>mdadm</code> using the <code>devtool build</code> command:

			$ devtool build mdadm
			Parsing recipes: 100% \|################################################################################################################\| ETA: 00:00:00
			Parsing of 872 .bb files complete (0 cached, 872 parsed). 1302 targets, 48 skipped, 0 masked, 0 errors.
			NOTE: Resolving any missing task queue dependencies
			NOTE: Preparing RunQueue
			NOTE: Executing SetScene Tasks
			NOTE: Executing RunQueue Tasks
			mdadm-3.4-r0 do_compile: NOTE: mdadm: compiling from external source tree /home/username/poky_sdk/workspace/sources/mdadm
			NOTE: Tasks Summary: Attempted 347 tasks of which 336 didn't need to be rerun and all succeeded.

			4. Take note that QEMU is still assumed to be running in the shell from the previous section; use the <code>devtool deploy-target</code> command to deploy the freshly-built <code>mdadm</code> module to the already-running image:

			$ devtool deploy-target mdadm root@192.168.7.2
			NOTE: Successfully deployed /home/username/poky_sdk/tmp/work/core2-64-poky-linux/mdadm/3.4-r0/image
			5. In the shell running QEMU, verify your changes by running “mdadm” and providing the “-V” option to return the version:

			sh-4.3# mdadm -V
			mdadm - v 3.4-modified 21 June 2016
			sh-4.3#

			'''NOTE''': If you try to use the previous command to see the original version of <code>mdadm</code>, you will get a message indicating the command is not found; <code>mdadm</code. is not in the image by default.

			6. At this point, you have modified the source code of an existing module all within your workspace. If you want to save your work, commit those changes. You can use the following commands to see the changes that need to be staged and committed:

			$ cd /$HOME/poky_sdk/workspace/sources/mdadm
			$ git status

			And these two commands to stage and commit the changed file:

			$ git add ReadMe.c
			$ git commit -m 'ReadMe.c-Updated-the-version-string'

			7. Turn the commit you have made into a patch:

			$ devtool update-recipe mdadm
			Parsing recipes..done.
			NOTE: Updating file run-ptest
			NOTE: Adding new patch 0001-ReadMe.c-Updated-the-version-string.patch
			NOTE: Updating recipe mdadm_3.4.bb

			The patch is located here:

			$HOME/poky_sdk/layers/build/meta/recipes-extended/mdadm/mdadm/0001-ReadMe.c-Updated-the-version-string.patch