OpenEmbedded-Core - Revision history

PaulEggleton: Content now moved to the OE wiki

2012-07-03T17:07:43Z

Content now moved to the OE wiki

← Older revision		Revision as of 17:07, 3 July 2012
Line 1:		Line 1:
	~~The~~ OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common among many different ~~Open Embedded~~ derived systems~~. While not all systems will use every piece~~ of the OpenEmbedded~~-Core, it will provide a self contained example that can be used to prove basic functionality~~.		OpenEmbedded-Core is a base layer of recipes, classes and associated files that is meant to be common among many different OpenEmbedded-derived systems and forms the basis of the new structure for OpenEmbedded.

	~~----~~		See the [http://www.openembedded.org/wiki/OpenEmbedded-Core OpenEmbedded-Core] page on the OpenEmbedded wiki for more information.

	~~Getting Started~~

	~~1) Download~~ the ~~repository~~
	~~<pre>~~
	~~git clone git://git.openembedded.org/openembedded-core oe-core~~
	~~cd oe-core~~
	~~git clone git~~://~~git~~.openembedded.org/~~bitbake bitbake~~
	~~</pre>~~

	~~2) Setup the environment, and build directory~~
	~~<pre>~~
	~~. .~~/oe-~~init~~-~~build-env [<build directory>~~]
	~~</pre>~~

	~~The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".~~

	~~3) First time configuration~~

	~~The first time you run oe-init-build-env, it will setup~~ the ~~directory~~ for ~~you. You should at least review the settings within the conf/local.conf file.~~

	~~4) Build something~~
	~~<pre>~~
	~~bitbake <rule>~~
	~~</pre>~~

	A good simple place to start is "bitbake core-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.

Tomparkin: Minimal image name is now "core-image-minimal" rather than "poky-image-minimal"

2011-05-10T14:15:37Z

Minimal image name is now "core-image-minimal" rather than "poky-image-minimal"

← Older revision		Revision as of 14:15, 10 May 2011
Line 28:		Line 28:
	</pre>		</pre>

	A good simple place to start is "bitbake ~~poky~~-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.		A good simple place to start is "bitbake core-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.

Tomparkin: Modified references to "poky-init-build-env" to "oe-init-build-env" in line with fa6176219b. Fixed a typo.

2011-05-10T11:29:42Z

Modified references to "poky-init-build-env" to "oe-init-build-env" in line with fa6176219b. Fixed a typo.

← Older revision		Revision as of 11:29, 10 May 2011
Line 1:		Line 1:
	The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common ~~amoung~~ many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.		The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common among many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.

	----		----
Line 14:		Line 14:
	2) Setup the environment, and build directory		2) Setup the environment, and build directory
	<pre>		<pre>
	. ./~~poky~~-init-build-env [<build directory>]		. ./oe-init-build-env [<build directory>]
	</pre>		</pre>

Line 21:		Line 21:
	3) First time configuration		3) First time configuration

	The first time you run ~~poky~~-init-build-env, it will setup the directory for you. You should at least review the settings within the conf/local.conf file.		The first time you run oe-init-build-env, it will setup the directory for you. You should at least review the settings within the conf/local.conf file.

	4) Build something		4) Build something

Ckamas: fixed spelling

2011-04-11T18:18:12Z

fixed spelling

← Older revision		Revision as of 18:18, 11 April 2011
Line 1:		Line 1:
	The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common ~~amount~~ many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.		The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common amoung many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.

	----		----

Jcdr: Fix for BBFETCH2=True is now commited, so the temporary step 1.5 is not need anymore.

2011-03-05T22:13:42Z

Fix for BBFETCH2=True is now commited, so the temporary step 1.5 is not need anymore.

← Older revision		Revision as of 22:13, 5 March 2011
Line 11:		Line 11:
	git clone git://git.openembedded.org/bitbake bitbake		git clone git://git.openembedded.org/bitbake bitbake
	</pre>		</pre>

	~~1.5) Temporary workaround (as of 2011-03-02)~~

	~~Edit the file scripts/poky-env-internal~~

	~~Add to the end:~~

	~~export BBFETCH2=True~~

	2) Setup the environment, and build directory		2) Setup the environment, and build directory

Jcdr: Using PRE tag to get a better display of the commands.

2011-03-05T22:05:21Z

Using PRE tag to get a better display of the commands.

← Older revision		Revision as of 22:05, 5 March 2011
Line 6:		Line 6:

	1) Download the repository		1) Download the repository
			<pre>
	git clone git://git.openembedded.org/openembedded-core oe-core		git clone git://git.openembedded.org/openembedded-core oe-core
	cd oe-core		cd oe-core
	git clone git://git.openembedded.org/bitbake bitbake		git clone git://git.openembedded.org/bitbake bitbake
			</pre>

	1.5) Temporary workaround (as of 2011-03-02)		1.5) Temporary workaround (as of 2011-03-02)
Line 20:		Line 21:

	2) Setup the environment, and build directory		2) Setup the environment, and build directory
			<pre>
	. ./poky-init-build-env [<build directory>]		. ./poky-init-build-env [<build directory>]
			</pre>

	The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".		The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".
Line 30:		Line 32:

	4) Build something		4) Build something
			<pre>
	bitbake <rule>		bitbake <rule>
			</pre>

	A good simple place to start is "bitbake poky-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.		A good simple place to start is "bitbake poky-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.

Mhatle at 23:28, 2 March 2011

2011-03-02T23:28:13Z

← Older revision		Revision as of 23:28, 2 March 2011
Line 1:		Line 1:
	[~~this page coming soon~~]		The OpenEmbedded-Core is a base layer, of recipes, classes and associated files that is meant to be common amount many different Open Embedded derived systems. While not all systems will use every piece of the OpenEmbedded-Core, it will provide a self contained example that can be used to prove basic functionality.

			----

			Getting Started

			1) Download the repository

			git clone git://git.openembedded.org/openembedded-core oe-core
			cd oe-core
			git clone git://git.openembedded.org/bitbake bitbake

			1.5) Temporary workaround (as of 2011-03-02)

			Edit the file scripts/poky-env-internal

			Add to the end:

			export BBFETCH2=True

			2) Setup the environment, and build directory

			. ./poky-init-build-env [<build directory>]

			The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".

			3) First time configuration

			The first time you run poky-init-build-env, it will setup the directory for you. You should at least review the settings within the conf/local.conf file.

			4) Build something

			bitbake <rule>

			A good simple place to start is "bitbake poky-image-minimal". This will run through a simple build and do basic system sanity checks. If your system needs additional software installed, or other environment settings it will tell you what is needed.

Jefro: new page

2011-03-01T18:45:58Z

new page

New page

[this page coming soon]