Building your own recipes from first principles - Revision history

Alen Sunnny Mathew: /* Overview */

2022-07-20T12:35:28Z

Overview

← Older revision		Revision as of 12:35, 20 July 2022
Line 1:		Line 1:
	= '''Yocto Project Quick Build''' =		= '''Yocto Project Quick Build''' =
	== ~~Overview~~ ==		== Kirkstone (4.0.2)==

	This walk-through has the aim of taking you from a clean system through to building and packaging an example project for inclusion in an image.		This walk-through has the aim of taking you from a clean system through to building and packaging an example project for inclusion in an image.

Alen Sunnny Mathew: /* Overview */

2022-07-20T12:33:43Z

Overview

← Older revision		Revision as of 12:33, 20 July 2022
Line 1:		Line 1:
			= '''Yocto Project Quick Build''' =
	== Overview ==		== Overview ==

Alen Sunnny Mathew: /* Build an example project on the host for testing (optional) */

2022-07-20T12:31:42Z

Build an example project on the host for testing (optional)

← Older revision		Revision as of 12:31, 20 July 2022
Line 139:		Line 139:
	Exit QEMU by either clicking on the shutdown icon or by typing Ctrl-C in the QEMU transcript window from which you evoked QEMU.		Exit QEMU by either clicking on the shutdown icon or by typing Ctrl-C in the QEMU transcript window from which you evoked QEMU.

	== Build an example project on the host for testing (optional) ==		= Build an example project on the host for testing (optional) =

	The most straightforward way to cross-compile projects for different targets within Yocto is to make use of [http://www.gnu.org/savannah-checkouts/gnu/automake/manual/html_node/index.html autotools]		The most straightforward way to cross-compile projects for different targets within Yocto is to make use of [http://www.gnu.org/savannah-checkouts/gnu/automake/manual/html_node/index.html autotools]

Alen Sunnny Mathew: /* Exit QEMU: */

2022-07-20T11:53:44Z

Exit QEMU:

← Older revision		Revision as of 11:53, 20 July 2022
Line 136:		Line 136:
	[https://docs.yoctoproject.org/dev-manual/qemu.html#using-the-quick-emulator-qemu The Quick EMUlator (QEMU)] Yocto Project Development Tasks Manual will gives you more understanding about running QEMU.		[https://docs.yoctoproject.org/dev-manual/qemu.html#using-the-quick-emulator-qemu The Quick EMUlator (QEMU)] Yocto Project Development Tasks Manual will gives you more understanding about running QEMU.

	= Exit QEMU: =		== Exit QEMU:==
	Exit QEMU by either clicking on the shutdown icon or by typing Ctrl-C in the QEMU transcript window from which you evoked QEMU.		Exit QEMU by either clicking on the shutdown icon or by typing Ctrl-C in the QEMU transcript window from which you evoked QEMU.

Alen Sunnny Mathew: /* Simulate Your Image Using QEMU */

2022-07-20T11:52:37Z

Simulate Your Image Using QEMU

← Older revision		Revision as of 11:52, 20 July 2022
Line 135:		Line 135:

	[https://docs.yoctoproject.org/dev-manual/qemu.html#using-the-quick-emulator-qemu The Quick EMUlator (QEMU)] Yocto Project Development Tasks Manual will gives you more understanding about running QEMU.		[https://docs.yoctoproject.org/dev-manual/qemu.html#using-the-quick-emulator-qemu The Quick EMUlator (QEMU)] Yocto Project Development Tasks Manual will gives you more understanding about running QEMU.

			= Exit QEMU: =
			Exit QEMU by either clicking on the shutdown icon or by typing Ctrl-C in the QEMU transcript window from which you evoked QEMU.

	== Build an example project on the host for testing (optional) ==		== Build an example project on the host for testing (optional) ==

Alen Sunnny Mathew: /* Simulate Your Image Using QEMU */

2022-07-20T11:51:20Z

Simulate Your Image Using QEMU

← Older revision		Revision as of 11:51, 20 July 2022
Line 131:		Line 131:

	== Simulate Your Image Using QEMU==		== Simulate Your Image Using QEMU==
			once the image is build , you can start QEMU with the following commands.
			$ runqemu qemux86-64

			[https://docs.yoctoproject.org/dev-manual/qemu.html#using-the-quick-emulator-qemu The Quick EMUlator (QEMU)] Yocto Project Development Tasks Manual will gives you more understanding about running QEMU.

	== Build an example project on the host for testing (optional) ==		== Build an example project on the host for testing (optional) ==

Alen Sunnny Mathew: /* Start the Build */

2022-07-20T11:46:34Z

Start the Build

← Older revision		Revision as of 11:46, 20 July 2022
Line 129:		Line 129:
	$ bitbake core-image-sato		$ bitbake core-image-sato
	For information on using the bitbake command, see the [https://docs.yoctoproject.org/overview-manual/concepts.html#bitbake BitBake] section in the Yocto Project Overview and Concepts Manual, or see The [https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-intro.html#the-bitbake-command BitBake Command] in the BitBake User Manual.		For information on using the bitbake command, see the [https://docs.yoctoproject.org/overview-manual/concepts.html#bitbake BitBake] section in the Yocto Project Overview and Concepts Manual, or see The [https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-intro.html#the-bitbake-command BitBake Command] in the BitBake User Manual.

			== Simulate Your Image Using QEMU==

	== Build an example project on the host for testing (optional) ==		== Build an example project on the host for testing (optional) ==

Alen Sunnny Mathew: /* Build a baseline image */

2022-07-20T11:40:12Z

Build a baseline image

← Older revision		Revision as of 11:40, 20 July 2022
Line 123:		Line 123:
	SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"		SSTATE_MIRRORS ?= "file://.* https://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"

	== Build ~~a baseline image~~ ==		== Start the Build==

	~~After configuring~~ the ~~environment you will be left~~ in ~~the build_qemux86 folder.~~		Continue with the following command to build an OS image for the target, which is core-image-sato in this example:

	~~You should then build a baseline image, which will take some time (numbers of hours)~~		$ bitbake core-image-sato
			For information on using the bitbake command, see the [https://docs.yoctoproject.org/overview-manual/concepts.html#bitbake BitBake] section in the Yocto Project Overview and Concepts Manual, or see The [https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-intro.html#the-bitbake-command BitBake Command] in the BitBake User Manual.
	$ bitbake core-image-~~minimal~~

	== Build an example project on the host for testing (optional) ==		== Build an example project on the host for testing (optional) ==

Alen Sunnny Mathew: /* Use Git to Clone Poky */

2022-07-20T11:36:19Z

Use Git to Clone Poky

← Older revision		Revision as of 11:36, 20 July 2022
Line 66:		Line 66:
	Already up-to-date.		Already up-to-date.

	For more options and information about accessing Yocto Project related repositories, see the ~~Locating Yocto Project Source Files~~ [https://docs.yoctoproject.org/dev-manual/start.html#locating-yocto-project-source-files] section in the Yocto Project Development Tasks Manual.		For more options and information about accessing Yocto Project related repositories, see the [https://docs.yoctoproject.org/dev-manual/start.html#locating-yocto-project-source-files Locating Yocto Project Source Files] section in the Yocto Project Development Tasks Manual.

	== Building Your Image ==		== Building Your Image ==

Alen Sunnny Mathew: /* Building Your Image */

2022-07-20T11:35:33Z

Building Your Image

← Older revision		Revision as of 11:35, 20 July 2022
Line 114:		Line 114:

	Tip:		Tip:
	You can significantly speed up your build and guard against fetcher failures by using ~~Shared State Cache~~ [https://docs.yoctoproject.org/overview-manual/concepts.html#shared-state-cache]mirrors and enabling ~~Hash Equivalence~~ [https://docs.yoctoproject.org/overview-manual/concepts.html#hash-equivalence]. This way, you can use pre-built artifacts rather than building them. This is relevant only when your network and the server that you use can download these artifacts faster than you would be able to build them.		You can significantly speed up your build and guard against fetcher failures by using [https://docs.yoctoproject.org/overview-manual/concepts.html#shared-state-cache Shared State Cache] mirrors and enabling [https://docs.yoctoproject.org/overview-manual/concepts.html#hash-equivalence Hash Equivalence ]. This way, you can use pre-built artifacts rather than building them. This is relevant only when your network and the server that you use can download these artifacts faster than you would be able to build them.

	To use such mirrors, uncomment the below lines in your conf/local.conf file in the ~~Build Directory~~ [https://docs.yoctoproject.org/ref-manual/terms.html#term-Build-Directory]:		To use such mirrors, uncomment the below lines in your conf/local.conf file in the [https://docs.yoctoproject.org/ref-manual/terms.html#term-Build-Directory Build Directory ]:

	BB_SIGNATURE_HANDLER = "OEEquivHash"		BB_SIGNATURE_HANDLER = "OEEquivHash"