Developer Workflow Improvements - Revision history

Yoann Congal: /* Configure */ small typo

2023-01-24T19:52:51Z

Configure: small typo

← Older revision		Revision as of 19:52, 24 January 2023
Line 81:		Line 81:
	The URL for the eSDK sstate mirror is not included in the above settings as it would conflict with the mirror used by the main build system. To handle this conflict, the value in put into a separate conf file <tt>conf/sdk-extra.conf</tt>		The URL for the eSDK sstate mirror is not included in the above settings as it would conflict with the mirror used by the main build system. To handle this conflict, the value in put into a separate conf file <tt>conf/sdk-extra.conf</tt>
	SSTATE_MIRRORS = "file://.* http://my.server.com/path/to/sstate-cache/PATH"		SSTATE_MIRRORS = "file://.* http://my.server.com/path/to/sstate-cache/PATH"
	Note that if you are using ~~Toasrter~~, you don't have access to <tt>conf/sdk-extra.conf</tt>, so you have to set variables via the U/I. This means that Toaster cannot have an sstate mirror for the OS build and set the eSDK's as follows:		Note that if you are using Toaster, you don't have access to <tt>conf/sdk-extra.conf</tt>, so you have to set variables via the U/I. This means that Toaster cannot have an sstate mirror for the OS build and set the eSDK's as follows:
	SDK_LOCAL_CONF_WHITELIST = "SSTATE_MIRRORS"		SDK_LOCAL_CONF_WHITELIST = "SSTATE_MIRRORS"
	SSTATE_MIRRORS = "file://.* http://my.server.com/path/to/sstate-cache/PATH"		SSTATE_MIRRORS = "file://.* http://my.server.com/path/to/sstate-cache/PATH"

	=== Build ===		=== Build ===

Henry Bruce: /* Layer Maintenance */

2017-06-17T01:05:05Z

Layer Maintenance

← Older revision		Revision as of 01:05, 17 June 2017
Line 6:		Line 6:

	== Layer Maintenance ==		== Layer Maintenance ==
	* This ~~tasks~~ is mainly bug fixing recipes and upgrading to never versions. It also includes building images that exercise the ~~layers~~ under test		* This workflow is mainly bug fixing recipes and upgrading to never versions. Updated recipes are then submitted to layer maintainers. It also includes building images that exercise the recipes under test.
	* Typically this is done in the distro maintainer (i.e. bitbake) environment, but ~~if no extra layers are to be added then~~ the extensible SDK is a better option as it ~~ensures a~~ common development environment.		* Typically this is done in the distro maintainer (i.e. bitbake) environment, but the extensible SDK can be a better option as it enables an easy to configure common development environment.

	== Application Development ==		== Application Development ==

Henry Bruce: /* Layer Maintenance */

2017-06-17T01:01:40Z

Layer Maintenance

← Older revision		Revision as of 01:01, 17 June 2017
Line 6:		Line 6:

	== Layer Maintenance ==		== Layer Maintenance ==
	* ~~Layers~~ and ~~recipes are edited as necessary~~. ~~Poky or Toaster is used to build image~~ that ~~exercises~~ layers under test		* This tasks is mainly bug fixing recipes and upgrading to never versions. It also includes building images that exercise the layers under test
			* Typically this is done in the distro maintainer (i.e. bitbake) environment, but if no extra layers are to be added then the extensible SDK is a better option as it ensures a common development environment.

	== Application Development ==		== Application Development ==

Henry Bruce: /* Build OS image */

2017-01-04T18:46:08Z

Build OS image

← Older revision		Revision as of 18:46, 4 January 2017
Line 59:		Line 59:

	== Build OS image ==		== Build OS image ==
	We recommend that you first [https://github.com/crops/docker-win-mac-docs/wiki install docker] on your OS of choice and then follow instructions to set up [https://github.com/crops/poky-container/blob/master/README.md Poky] or [https://github.com/crops/toaster-container/blob/master/README.md Toaster] containers. However, these instructions will work for Poky or Toaster on Linux but you're on your own for installation and configuration.		We recommend that you first [https://github.com/crops/docker-win-mac-docs/wiki install docker] on your OS of choice and then follow instructions to set up [https://github.com/crops/poky-container/blob/master/README.md Poky] or [https://github.com/crops/toaster-container/blob/master/README.md Toaster] containers. However, these instructions will work for Poky or Toaster on Linux directly but you're on your own for installation and configuration.

	Now add layers and configure so you can build your image.		Now add layers and configure so you can build your image.

Henry Bruce: /* Instructions for Workflow in Current Form */

2017-01-03T23:38:32Z

Instructions for Workflow in Current Form

← Older revision		Revision as of 23:38, 3 January 2017
Line 54:		Line 54:

	= Instructions for Workflow in Current Form =		= Instructions for Workflow in Current Form =
	If you are inside a corporate firewall, install and configure the [https://github.com/crops/chameleonsocks Chameleonsocks] container based proxy solution~~. Then [https://github.com/crops/docker-win-mac-docs/wiki install docker]~~.		If you are inside a corporate firewall, install and configure the [https://github.com/crops/chameleonsocks Chameleonsocks] container based proxy solution.

	You have choice between using the Yocto Project tools on the command line with the Poky container or by using the Toaster web interface. Toaster is easier to get going but most needs more work to get the best of out interface (see section below), so these instructions will assume use of the command line.		You have choice between using the Yocto Project tools on the command line with the Poky container or by using the Toaster web interface. Toaster is easier to get going but most needs more work to get the best of out interface (see section below), so these instructions will assume use of the command line.

Henry Bruce: /* Workflow Vision */

2017-01-03T23:36:28Z

Workflow Vision

← Older revision		Revision as of 23:36, 3 January 2017
Line 16:		Line 16:
	This section calls out the workflows in more detail, describing specific use of tools in each step.		This section calls out the workflows in more detail, describing specific use of tools in each step.

	The set-up instructions at the end of this page represent the "what can currently be done" version of the workflows.		The [[Developer Workflow Improvements#Instructions for Workflow in Current Form \| set-up instructions]] at the end of this page represent the "what can currently be done" version of the workflows.

	== Build OS Image ==		== Build OS Image ==

Henry Bruce: /* Workflow Vision */

2017-01-03T23:34:13Z

Workflow Vision

← Older revision		Revision as of 23:34, 3 January 2017
Line 15:		Line 15:
	= Workflow Vision =		= Workflow Vision =
	This section calls out the workflows in more detail, describing specific use of tools in each step.		This section calls out the workflows in more detail, describing specific use of tools in each step.

			The set-up instructions at the end of this page represent the "what can currently be done" version of the workflows.

	== Build OS Image ==		== Build OS Image ==
	# On OS of your choice start containerized Poky or Toaster instance.		# On OS of your choice start containerized Poky or Toaster instance.

Henry Bruce: /* Application Development */

2017-01-03T23:34:00Z

Application Development

← Older revision		Revision as of 23:34, 3 January 2017
Line 12:		Line 12:
	* A developer uses resulting eSDK to create/modify an application by using devtool (iterative process).		* A developer uses resulting eSDK to create/modify an application by using devtool (iterative process).
	* Once application is complete its recipe is added to a layer and Toaster is used to build an image that includes it		* Once application is complete its recipe is added to a layer and Toaster is used to build an image that includes it

	~~The set-up instructions at the end of this page represent the "what can currently be done" version of the workflows.~~

	= Workflow Vision =		= Workflow Vision =

Henry Bruce: /* Application Development */

2017-01-03T23:33:31Z

Application Development

← Older revision		Revision as of 23:33, 3 January 2017
Line 12:		Line 12:
	* A developer uses resulting eSDK to create/modify an application by using devtool (iterative process).		* A developer uses resulting eSDK to create/modify an application by using devtool (iterative process).
	* Once application is complete its recipe is added to a layer and Toaster is used to build an image that includes it		* Once application is complete its recipe is added to a layer and Toaster is used to build an image that includes it

	There are two personas in this scenario; 'os-dev' who maintains the OS image and generates its extensible SDK and the 'app-dev' who creates new applications to run on OS. The scenario assumes that an early version of the application exists but it needs features added and to be integrated into OS image. We recognize that in smaller organizations the roles of os-dev and app-dev may be blurry but the concept of two separate personas simplifies description of workflow.

	The set-up instructions at the end of this page represent the "what can currently be done" version of the workflows.		The set-up instructions at the end of this page represent the "what can currently be done" version of the workflows.

Henry Bruce: /* Introduction */

2017-01-03T23:23:47Z

Introduction

← Older revision		Revision as of 23:23, 3 January 2017
Line 1:		Line 1:
	Back to Yocto Project [[Main Page]]		Back to Yocto Project [[Main Page]]
	= Introduction =		= Introduction =
	The page describes how new tools such as [https://www.gitbook.com/book/dnplas/yocto-project-crops/details Cross Platform Support] (CROPS), [http://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-extensible-sdk-intro Extensible SDK] (eSDK), [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-modifying-source-code devtool] and [https://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html#toaster-manual-intro Toaster] make it easier to get the best out of Yocto.		The page describes how new tools such as [https://www.gitbook.com/book/dnplas/yocto-project-crops/details Cross Platform Support] (CROPS), [http://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-extensible-sdk-intro Extensible SDK] (eSDK), [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-modifying-source-code devtool] and [https://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html#toaster-manual-intro Toaster] make it easier to get the best out of Yocto. To benefit from this article the reader must be comfortable with the basics of the Yocto Project (i.e. has gone through [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Quick Start Guide] and knows how to add packages to an image).

	To benefit from this article the reader must be comfortable with the basics of the Yocto Project (i.e. has gone through [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Quick Start Guide] and knows how to add packages to an image).

	We envisage two distinct workflows, layer maintenance and application development.		We envisage two distinct workflows, layer maintenance and application development.