OpenEmbedded - Revision history

Pundiramit: /* Building an Image */

2010-01-18T07:03:06Z

‎Building an Image

2010-01-14T06:50:55Z

‎local.conf

2009-12-27T08:10:22Z

‎Screen is Your Friend: linkchg

2009-07-19T11:15:10Z

catchg

2009-05-13T23:49:24Z

‎${OE_HOME}

2009-05-13T20:20:36Z

‎local.conf

2009-05-13T20:18:53Z

‎local.conf: note on SRCPV in site.conf

2009-05-13T20:06:23Z

‎local.conf: It's recipes, these days, not packages

2009-04-20T17:10:10Z

‎Synchronizing OpenEmbedded With Git

2009-04-20T15:46:24Z

‎local.conf

@@ Line 168: / Line 168: @@
 A good place to start is with
-  bitbake fso-image
+  bitbake fso-illume-image
 That concludes this introduction to BitBake and OpenEmbedded. Good luck!

@@ Line 103: / Line 103: @@
 '''Note:''' Using BitBake and OE for cross-compilation require that each target-distro combination is built in a separate directory, so that no version collisions occur. Concurrent builds may safely share the same DL_DIR though. This would suggest that a safe name for build directories is of the form ${OE_HOME}/build-${MACHINE}-${DISTRO}. Of course, if you don't plan on building for more than one machine-distro combination, then the naming of this directory is arbitrary. For the purpose of this example, we will use the convention ${OE_HOME}/build-${MACHINE} .
-Now, create the 'local.conf' configuration file. Notice that the CACHE and TMPDIR variables are neatly kept within the build directory while the DL_DIR variable is outside of the build directory, so that concurrent builds may reuse the same source packages.
+Now, create the 'local.conf' configuration file. Notice that the CACHE and TMPDIR variables are neatly kept within the build directory while the DL_DIR variable is outside of the build directory, so that concurrent builds may reuse the same source packages. Copy 'local.conf' to ${OE_HOME}/org.openembedded.dev/conf.
 <pre>
   OE_HOME ?= "${HOME}/oe"

@@ Line 214: / Line 214: @@
 If you happen to be building all of your packages remotely on a server, using an ssh session, the session might occasionally be interrupted and the connection could be terminated. A similar event could occur if your X server suddenly craches. If in the process of building an image with bitbake, this means that the build process will terminate as well.
-In order to ensure that a build continues in the presence of communication failures, it is advisable to use the [http://www.gnu.org/software/screen GNU Screen] utility. Screen is also very useful when performing several concurrent OpenEmbedded builds for different machine-distro combinations.
+In order to ensure that a build continues in the presence of communication failures, it is advisable to use the [[GNU Screen]] utility. Screen is also very useful when performing several concurrent OpenEmbedded builds for different machine-distro combinations.
 Screen installation varies with your OS and distribution.

@@ Line 321: / Line 321: @@
 </pre>
-[[Category:Application Developer]]
+[[Category:Developer resources]]
-[[Category:System Developers]]

@@ Line 42: / Line 42: @@
   setenv OE_HOME ${HOME}/oe
 Next, run 'mkdir -p ${OE_HOME}' to create the directory.
 === Synchronizing OpenEmbedded With Git ===

@@ Line 132: / Line 132: @@
 ERROR: EOL while scanning string literal (<string>, line 1) while parsing .../openmoko/org.openembedded.dev/recipes/freesmartphone/frameworkd_git.bb
 </pre>
 === setup-env ===

← Older revision		Revision as of 20:18, 13 May 2009
Line 123:		Line 123:

	The BBFILES variable is also of prime importance! It tells bitbake where to locate all available recipes for a build. The OpenEmbedded build environment is almost completely ready to go, with just one more minor step left.		The BBFILES variable is also of prime importance! It tells bitbake where to locate all available recipes for a build. The OpenEmbedded build environment is almost completely ready to go, with just one more minor step left.
		+
		+	If you're not using a distro-provided makefile setup, and your site.conf (or local.conf) doesn't include the line
		+	<pre>
		+	SRCPV = "${@bb.fetch.get_srcrev(d)}"
		+	</pre>
		+	then you may find bitbake complaining along the lines of
		+	<pre>
		+	ERROR: EOL while scanning string literal (<string>, line 1) while parsing .../openmoko/org.openembedded.dev/recipes/freesmartphone/frameworkd_git.bb
		+	</pre>

	=== setup-env ===		=== setup-env ===

@@ Line 110: / Line 110: @@
   DL_DIR = "${OE_HOME}/downloads"
-  BBFILES := "${OE_HOME}/org.openembedded.dev/packages/*/*.bb"
+  BBFILES := "${OE_HOME}/org.openembedded.dev/recipes/*/*.bb"
   BBMASK = ""

@@ Line 59: / Line 59: @@
   cd ${OE_HOME}/org.openembedded.dev
   git pull
 </pre>

@@ Line 100: / Line 100: @@
   MACHINE = "om-gta02"
-  DISTRO = "angstrom-2008.1"
+  DISTRO = "openmoko"
   DL_DIR = "${OE_HOME}/downloads"