Building and Customizing EMAC OE - Revision history

Bserrano at 20:53, 2 April 2014

2014-04-02T20:53:26Z

Bserrano at 20:32, 27 March 2014

2014-03-27T20:32:39Z

Bserrano at 22:31, 4 March 2014

2014-03-04T22:31:36Z

Mwelling at 20:17, 3 January 2014

2014-01-03T20:17:03Z

Kyoungmeyer at 20:08, 3 January 2014

2014-01-03T20:08:52Z

Kyoungmeyer at 19:45, 3 January 2014

2014-01-03T19:45:52Z

Mdean: Fixed message box icon.

2014-01-03T19:12:25Z

Fixed message box icon.

Mdean: Updated disclaimer.

2014-01-03T19:10:30Z

Updated disclaimer.

Mdean: Added missing datestamp.

2014-01-03T00:22:21Z

Added missing datestamp.

Mdean: Minor fixes; marked Complete.

2014-01-03T00:20:18Z

Minor fixes; marked Complete.

@@ Line 1: / Line 1: @@
-{{todo|SEOKWREV <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+);(03.04.14-16:30->BS-);(03.27.14-15:30->BS+)|Michael Gloff|project=oe 4,mg,SEOKWREV,ky,md,bs}}
+{{todo|SEOKWREV <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+);(03.04.14-16:30->BS-);(03.27.14-15:30->BS+);(04.02.14-15:50->BS+)|Michael Gloff|project=oe 4,mg,SEOKWREV,ky,md,bs}}
 {{#seo:
 |title=Building and Customizing EMAC OE
 |titlemode=append
-|keywords=Building,Customizing,EMAC OE,Installing BitBake,Installing EMAC OpenEmbedded
+|keywords=Building EMAC OE,Customizing EMAC OE,Installing BitBake,Installing EMAC OpenEmbedded
 |description=Building and Customizing EMAC open embedded.
 }}

← Older revision		Revision as of 20:32, 27 March 2014
Line 1:		Line 1:
−	{{todo\|~~SEOKWTODO~~ <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+);(03.04.14-16:30->BS-)\|Michael Gloff\|project=oe 4,mg,~~SEOKWTODO~~,ky,md,bs}}	+	{{todo\|SEOKWREV <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+);(03.04.14-16:30->BS-);(03.27.14-15:30->BS+)\|Michael Gloff\|project=oe 4,mg,SEOKWREV,ky,md,bs}}

		+	{{#seo:
		+	\|title=Building and Customizing EMAC OE
		+	\|titlemode=append
		+	\|keywords=Building,Customizing,EMAC OE,Installing BitBake,Installing EMAC OpenEmbedded
		+	\|description=Building and Customizing EMAC open embedded.
		+	}}
	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

← Older revision		Revision as of 22:31, 4 March 2014
Line 1:		Line 1:
−	{{todo\|~~Complete~~ <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+)\|Michael Gloff\|project=oe 4,mg,~~complete~~,ky,md}}	+	{{todo\|SEOKWTODO <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+);(03.04.14-16:30->BS-)\|Michael Gloff\|project=oe 4,mg,SEOKWTODO,ky,md,bs}}

	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

← Older revision		Revision as of 20:17, 3 January 2014
Line 1:		Line 1:
−	{{todo\|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+)\|Michael Gloff\|project=oe 4,mg,complete,ky,md}}	+	{{todo\|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+);(01.03.14-14:15->MW+)\|Michael Gloff\|project=oe 4,mg,complete,ky,md}}

	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

← Older revision		Revision as of 20:08, 3 January 2014
Line 1:		Line 1:
−	{{todo\|~~Final Draft~~ <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+)\|Michael Gloff\|project=oe 4,mg,~~finaldraft~~,ky,md}}	+	{{todo\|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+)\|Michael Gloff\|project=oe 4,mg,complete,ky,md}}

	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

← Older revision		Revision as of 19:45, 3 January 2014
Line 1:		Line 1:
−	{{todo\|~~Review~~ <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+)\|Michael Gloff\|project=oe 4,mg,~~Review~~,ky,md}}	+	{{todo\|Final Draft <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+);(01.03.14-13:10->MD+);(01.03.14-13:45->KY+)\|Michael Gloff\|project=oe 4,mg,finaldraft,ky,md}}

	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

@@ Line 5: / Line 5: @@
 Please familiarize yourself with [http://www.openembedded.org/wiki/Main_Page OpenEmbedded's Wiki] before continuing.
-{{ mbox | type = important | style = margin-bottom: 1em;| text = Caution should be exercised when making changes to a build as outlined below. It is possible, if directions are not followed carefully, to "Brick" the system (potentially requiring the return of the board to EMAC for restoration).}}
+{{ mbox | type = warning | style = margin-bottom: 1em;| text = Caution should be exercised when making changes to a build as outlined below. It is possible, if directions are not followed carefully, to "Brick" the system (potentially requiring the return of the board to EMAC for restoration).}}
 ==System Preparation==

← Older revision		Revision as of 00:22, 3 January 2014
Line 1:		Line 1:
−	{{todo\|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+)\|Michael Gloff\|project=oe 4,mg,Complete,ky,md}}	+	{{todo\|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+);(01.02.14-18:20->MD+)\|Michael Gloff\|project=oe 4,mg,Complete,ky,md}}

	An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.		An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.

@@ Line 1: / Line 1: @@
-{{todo|Final Draft <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+)|Michael Gloff|project=oe 4,mg,finaldraft,ky,md}}
+{{todo|Complete <strike>Broken Links and info boxes; recommends Debian 5.0; Poor transition from background info into howto steps; tries too hard to be distro neutral; only provides dependency info for Debian; we should mirror bitbake and update the links, so the links won't break; still shows using svn for OE</strike> (12.31.13-11:15->KY+)|Michael Gloff|project=oe 4,mg,Complete,ky,md}}
 An EMAC [http://www.openembedded.org/ OpenEmbedded] Linux build is the end product of several different build systems. These consist of three core components: BitBake, OpenEmbedded, and EMAC . Each one of these tools is built one upon the other: BitBake → OpenEmbedded → EMAC OpenEmbedded. You will need to download each component separately.
@@ Line 9: / Line 9: @@
 ==System Preparation==
-{{ mbox | type = warning | style = margin-bottom: 1em;| text = After initial preparation, only run the commands on this page from a user in the oe group. Doing so can do serious damage to the running operating system.}}
+{{ mbox | type = warning | style = margin-bottom: 1em;| text = After initial preparation, the commands on this page should only be run as a user in the oe group. Doing otherwise can cause serious damage to the running operating system.}}
 You need to be running a GNU/Linux operating system to use OpenEmbedded. OpenEmbedded requires a large number of development tools to work correctly with your Linux distribution. However due to the large number of distributions available, please see the OpenEmbedded Wiki page [http://www.openembedded.org/wiki/Getting_started_with_OE-Classic OE and Your Distro] for the instruction on the installation of the development packages which are required.
-After installing all of the necessary packages to your distribution you will need to set up the location of EMAC OE. By default EMAC OE expects to be installed in <code>/opt/oe</code>.
+After installing all of the necessary packages to your distribution you will need to set up the location of EMAC OE. The default EMAC OE install location is <code>/opt/oe</code>.
-As the superuser (root or as sudo):
+As the superuser (root or via sudo):
 # Create a group called <code>oe</code> and add the development users to the group.
 # Make a directory in <code>/opt</code> called <code>oe</code>.
@@ Line 22: / Line 22: @@
 <syntaxhighlight lang="bash">
-developer@ldc:~$ add-group oe developer
+root@ldc:~# add-group oe developer
-developer@ldc:~$ mkdir /opt/oe
+root@ldc:~# mkdir /opt/oe
-developer@ldc:~$ chmod 6775 /opt/oe
+root@ldc:~# chmod 6775 /opt/oe
-developer@ldc:~$ oe /opt/oe
+root@ldc:~# oe /opt/oe
 </syntaxhighlight>
@@ Line 122: / Line 122: @@
 Run the emac-image image recipe.
 <syntaxhighlight lang="bash">
 developer@ldc:~$ ./oe-run.sh emac-image
 </syntaxhighlight>
 Bitbake performs a sanity check on the system each time that it is run. If any misconfigurations are detected, the user will be notified of the issue and a suggested fix. Depending on the system, there may be several issues to correct on the first run. For example, a common issue is the value of <code>/proc/sys/vm/mmap_min_addr</code>, as illustrated below:
@@ Line 141: / Line 143: @@
 EMAC recommends fixing this issue as suggested, but the user should be aware of the possible security implications.
-On the first build, bitbake will create a cache of the recipes in the build system, which will take a few minutes. After this is complete, bitbake attempts to run all of the recipes required for the image to be built. This is done in multiple threads utilizing the dependencies between recipes to determine which packages are built first. The first task is to “fetch” the software required to build each recipe. This may take a while depending on the network connection speed. After the source is downloaded the first time, any further builds will use the existing local source copy rather than downloading the source again.
+On the first build, bitbake will create a cache of the recipes in the build system; this will take a few minutes. After this is complete, bitbake attempts to run all of the recipes required for the image to be built. This is done in multiple threads utilizing the dependencies between recipes to determine which packages are built first. The first task is to “fetch” the software required to build each recipe. This may take a while depending on the network connection speed. After the source is downloaded the first time, any further builds will use the existing local source copy rather than downloading the source again.
 Occasionally, project maintainers or mirrors will move or obsolete a source download such that the location specified in the recipe <code>SRC_URI</code> is no longer valid. If this happens, bitbake will print an error and stop the build. For example, the following error occurred when the zlib version 1.2.3 recipe was run:
@@ Line 176: / Line 178: @@
 ====x86 Image Install====
-This example is for x86 based single board computers only using a CompactFlash SSD. For other boards contact EMAC Technical Support. See [[Loading Linux Images to a Compact Flash_Disk]]
+This example is for x86 based single board computers only using a CompactFlash disk. For other boards contact EMAC Technical Support. See [[Loading Linux Images to a Compact Flash_Disk]]
 ====ARM Image Install====