BitBake/UserManual - Revision history

Wmat: /* Working TOC */

2013-01-15T15:24:41Z

Working TOC

← Older revision		Revision as of 15:24, 15 January 2013
Line 18:		Line 18:
	#Introduction		#Introduction
	##History and Goals		##History and Goals
	##Concepts - This ~~chapter~~ will introduce the relationship between the BitBake executable and the metadata file types. I'll introduce Layers here as well.		##Concepts - This section will introduce the relationship between the BitBake executable and the metadata file types. I'll introduce Layers here as well.
	#BitBake Quickstart - this Chapter will include 2-3 real world examples.		#BitBake Quickstart - this Chapter will include 2-3 real world examples.
	## Hello World - documents the development of a Hello World BitBake example, exclusive of OE or Yocto.		## Hello World - documents the development of a Hello World BitBake example, exclusive of OE or Yocto.

Wmat: Working out new document structure.

2013-01-15T15:10:56Z

Working out new document structure.

@@ Line 11: / Line 11: @@
 # File Download Support
 # The bitbake command
 == What to Include? ==

Rpjday: /* Random observations by rday */

2013-01-09T12:31:10Z

Random observations by rday

← Older revision		Revision as of 12:31, 9 January 2013
Line 32:		Line 32:

	* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>" is, of course, used massively and should be documented.		* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>" is, of course, used massively and should be documented.

			* Variables that probably deserve more coverage:
			** <tt>BB_DANGLINGAPPENDS_WARNONLY = "1"</tt>

	== Deprecated/weird/dead stuff ==		== Deprecated/weird/dead stuff ==

Wmat: /* Introduction */

2013-01-04T02:59:27Z

Introduction

← Older revision		Revision as of 02:59, 4 January 2013
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	The current BitBake User Manual, as of Dec. 31, 2012 is quite out dated. This page serves a a place to collect ideas for revisions that are required to ~~the~~ bring the User Manual up to date.		The current BitBake User Manual, as of Dec. 31, 2012 is quite out dated. This page serves a a place to collect ideas for revisions that are required to bring the User Manual up to date.

	== Current TOC ==		== Current TOC ==

Wmat: Added a bit about Hob.

2013-01-02T13:39:08Z

Added a bit about Hob.

← Older revision		Revision as of 13:39, 2 January 2013
Line 38:		Line 38:
	* All "pnum=" should now be replaced with "striplevel=" in SRC_URI for patches.		* All "pnum=" should now be replaced with "striplevel=" in SRC_URI for patches.
	* Current BitBake manual shows a "this=ignored" parm for patches; total mystery what that means, nothing uses it, Chris Larson has no idea what it's for. Ignore it.		* Current BitBake manual shows a "this=ignored" parm for patches; total mystery what that means, nothing uses it, Chris Larson has no idea what it's for. Ignore it.

			== Add Hob Documentation ==

			With Hob getting better and better, it would seem appropriate to include a chapter in the Bitbake User Manual documenting it.

Rpjday: /* Deprecated/weird/dead stuff */

2013-01-02T13:32:45Z

Deprecated/weird/dead stuff

← Older revision		Revision as of 13:32, 2 January 2013
Line 35:		Line 35:
	== Deprecated/weird/dead stuff ==		== Deprecated/weird/dead stuff ==

	* All "proto=" should now be replaced with "protocol=", although the old form is still allowed but deprecated.		* All "proto=" should now be replaced with "protocol=" in SRC_URI, although the old form is still allowed but deprecated.
	* All "pnum=" should now be replaced with "striplevel=" for patches.		* All "pnum=" should now be replaced with "striplevel=" in SRC_URI for patches.
	* Current BitBake manual shows a "this=ignored" parm for patches; total mystery what that means, nothing uses it.		* Current BitBake manual shows a "this=ignored" parm for patches; total mystery what that means, nothing uses it, Chris Larson has no idea what it's for. Ignore it.

Rpjday: /* Random observations by rday */

2013-01-02T13:08:28Z

Random observations by rday

← Older revision		Revision as of 13:08, 2 January 2013
Line 31:		Line 31:
	* While BitBake fetcher supports numerous fetching protocols, only half of them are even used so I would simply ignore the unused ones. I made a bunch of notes on fetching [http://www.crashcourse.ca/wiki/index.php/BitBake_fetching_and_patching here].		* While BitBake fetcher supports numerous fetching protocols, only half of them are even used so I would simply ignore the unused ones. I made a bunch of notes on fetching [http://www.crashcourse.ca/wiki/index.php/BitBake_fetching_and_patching here].

	* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>", is ~~used massively~~, of course and should be documented.		* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>" is, of course, used massively and should be documented.

	== Deprecated/weird/dead stuff ==		== Deprecated/weird/dead stuff ==

Rpjday: /* Deprecated/weird/dead stuff */

2013-01-02T13:07:53Z

Deprecated/weird/dead stuff

← Older revision		Revision as of 13:07, 2 January 2013
Line 37:		Line 37:
	* All "proto=" should now be replaced with "protocol=", although the old form is still allowed but deprecated.		* All "proto=" should now be replaced with "protocol=", although the old form is still allowed but deprecated.
	* All "pnum=" should now be replaced with "striplevel=" for patches.		* All "pnum=" should now be replaced with "striplevel=" for patches.
			* Current BitBake manual shows a "this=ignored" parm for patches; total mystery what that means, nothing uses it.

Rpjday: /* Random observations by rday */

2013-01-02T13:06:50Z

Random observations by rday

← Older revision		Revision as of 13:06, 2 January 2013
Line 32:		Line 32:

	* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>", is used massively, of course and should be documented.		* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>", is used massively, of course and should be documented.

			== Deprecated/weird/dead stuff ==

			* All "proto=" should now be replaced with "protocol=", although the old form is still allowed but deprecated.
			* All "pnum=" should now be replaced with "striplevel=" for patches.

Rpjday: /* Random observations by rday */

2013-01-02T13:05:28Z

Random observations by rday

← Older revision		Revision as of 13:05, 2 January 2013
Line 29:		Line 29:
	== Random observations by rday ==		== Random observations by rday ==

	* While BitBake fetcher supports numerous fetching protocols, only half of them are even used so I would simply ignore the unused ones. I made a bunch of notes on fetching [http://www.crashcourse.ca/wiki/index.php/BitBake_fetching_and_patching here]..		* While BitBake fetcher supports numerous fetching protocols, only half of them are even used so I would simply ignore the unused ones. I made a bunch of notes on fetching [http://www.crashcourse.ca/wiki/index.php/BitBake_fetching_and_patching here].

			* Section 2.2.1 of current BitBake manual opens with discussion of "VAR_<override>_append" construct; that appears to be simply [http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-January/003984.html broken and unused]. I would ignore it. The other form, "VAR_append_<override>", is used massively, of course and should be documented.