Yocto Project Introduction - Revision history

Tim Bird: /* Build work areas */ improve wording

2013-03-28T20:49:48Z

‎Build work areas: improve wording

2013-03-28T20:48:04Z

‎Build work areas: fix typo

2013-02-20T23:50:56Z

‎build variables

2012-11-20T19:02:44Z

2012-10-30T19:07:41Z

2012-10-30T18:57:44Z

‎the flow of control

2012-10-30T18:57:07Z

‎the flow of control: add link to variable glossary

2012-10-30T18:48:31Z

‎Build stages

2012-10-26T16:41:52Z

‎Build stages

2012-10-26T16:39:15Z

‎the flow of control

@@ Line 177: / Line 177: @@
 The work directory for a software component contains not only the source code for the item, but additional
 data related to building it, staging it for installation into a package or image, and a 'temp' directory
-which has logs of the various build tasks.  The work directory is useful to know if you want to customize
+which has logs of the various build tasks.  It is useful to know the work directory if you want to customize
 the software (for example if you need to make a bugfix or apply some external patch), or determine
 why some build operation (such as fetching, compiling, packaging, etc.) is failing.

@@ Line 163: / Line 163: @@
 the target architecture for the component.  During the build, some items are built for the host machine
 and some are built for the target machine.  In non-embedded Linux, the machine you build and debug on and the machine
-you compiler for (run the software on) are very often the same.  However, in embedded Linux these are often different machines,
+you compile for (run the software on) are very often the same.  However, in embedded Linux these are often different machines,
 and often they even have different CPU architectures.

← Older revision		Revision as of 23:50, 20 February 2013
Line 384:		Line 384:
	** The best place to start is by looking in the [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glos Poky Reference Manual variable glossary]		** The best place to start is by looking in the [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glos Poky Reference Manual variable glossary]

		+	* bitbake -e <recipe> \| grep "^S=" - print the source directory for a recipe
		+
		+	* bitbake -e <recipe> \| grep "^WORKDIR=" - print the working directory for a recipe

	== Comparison with other systems ==		== Comparison with other systems ==

@@ Line 6: / Line 6: @@
 curve for people approaching the Yocto Project for the first time is lessened.
-[''As of August 2012, this document is still under construction...'']
+[''As of November 2012, this document is still under construction...'']
 == The big picture ==
@@ Line 383: / Line 383: @@
 * How can one know all the different build variables there are, and how to set them?
 ** The best place to start is by looking in the [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glos Poky Reference Manual variable glossary]

@@ Line 65: / Line 65: @@
 Bitbake is written in Python, and some aspects of the build system can be written using short
 Python snippets as well.  Many aspects of the system are written in snippets of shell code as well.
 === The meta-data ===

@@ Line 377: / Line 377: @@
 ** bitbake -c listtasks <image-or-recipe-name>
-* How to know all the different build variables there are, and how to set them?
 ** The best place to start is by looking in the [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glos Poky Reference Manual variable glossary]

← Older revision		Revision as of 18:57, 30 October 2012
Line 378:		Line 378:

	* How to know all the different build variables there are, and how to set them?		* How to know all the different build variables there are, and how to set them?
−	** ~~'''UNKNOWN'''~~	+	** The best place to start is by looking in the [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-variables-glos Poky Reference Manual variable glossary]

@@ Line 106: / Line 106: @@
 === Build stages ===
 The recipes for a distribution define a number of discreet tasks that are performed to accomplish the build.
-The tasks have names such as 'fetchall', 'configure', 'compile'.  Internally, these tasks are prefixed with 'do_'
+The tasks have names such as 'fetch', 'configure', 'compile'.  Internally, these tasks are prefixed with 'do_'
 (eg. do_configure)

@@ Line 154: / Line 154: @@
 </pre>
-In general, a build proceed through the stages in order: fetching, configuring, compiling, installing, and packaging the
+In general, a build proceed through the stages in order: fetch, configure, compile, install, and package the
 software.

@@ Line 341: / Line 341: @@
 * How to know what images are available?
 ** ls meta*/recipe*/images/*.bb
 <pre>
-</pre>
 meta-hob/recipes-core/images/hob-image.bb
 meta/recipes-core/images/core-image-base.bb
@@ Line 367: / Line 366: @@
 meta-ti/recipes-misc/images/cloud9-image.bb
 meta-ti/recipes-misc/images/ti-hw-bringup-image.bb
-<pre>
+</pre>
 * How to know what recipes are available (overall)?