summaryrefslogtreecommitdiffstats
path: root/bitbake/doc
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: support $BITBAKE_UI environmentEnrico Scholz2012-05-231-0/+6
| | | | | | | | | | | | | | | | | Patch adds support for a $BITBAKE_UI environment variable which allows to configure the preferred user interface. Although an '-u' option (which will override the environment variable) exists already, it was required to specify this option on every invocation of bitbake. Because user interface is instanciated very early in the program it is not possible to use bitbake.conf for setting up a default. An environment variable (which acts in a similar category like $PAGER or $EDITOR) is a simple way for configuring the default. (Bitbake rev: e3c213015953d1a0afb5ef4be59e1264990e5cee) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix typo in user manual: "incarantion" -> "incarnation"Robert P. J. Day2012-04-061-1/+1
| | | | | | | (Bitbake rev: dd15a92a0932d3e177c0ca7b2923da1d72046e51) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* usermanual: Correct "inherit" search to bbclass from oeclassDarren Hart2012-01-201-1/+1
| | | | | | | | | Bitbake looks for bbclass now, not oeclass. Update the docs accordingly. (Bitbake rev: 8b713708541f85a4252c0f7b683aff4407c7d3e0) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update users of getVar/setVar to use the data store functions directlyRichard Purdie2011-11-271-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* doc: update manual for checksum changesJoshua Lock2011-10-241-1/+1
| | | | | | | | | Document the ability to use SRC_URI parameters for checksums (Bitbake rev: 0a6443f9e1d07865c9fd1dfc0b4622eb1c4c3f3a) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* usermanual: The git fetcher defaults to the git protocol (or file)Richard Purdie2011-08-231-1/+1
| | | | | | (Bitbake rev: 692c2fcead5c82249359ad54d2c7941d087a2eb3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/usermanual: Update to be more in sync with bitbake codebaseRichard Purdie2011-08-111-28/+108
| | | | | | (Bitbake rev: 6c382c2ee7740a5e78b4135648870e5c181ec23f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* doc/usermanual.xml: Tweaks for the manualBrandon Stafford2011-06-221-67/+66
| | | | | | | | | | | This patch contains what I hope are non-controversial improvements to the manual. Most of the changes are single characters, but the line-by-line diff makes the patch look large. (Bitbake rev: 5481cc90645e13c4e3cdea41e8e369528a0b1649) Signed-off-by: Brandon Stafford <brandon@pingswept.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop psyco supportRichard Purdie2011-06-092-5/+0
| | | | | | | | | | | At best it gave 1-2% improvement now, its 32 bit x86 only and isn't supported after python 2.6. PyPy is probably a better option now. (Bitbake rev: 3c3bd0c2fa80d747f25401c17b785c7c2f3787ca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake manual: fix typoBernhard Reutner-Fischer2011-05-061-2/+2
| | | | | | | | | "is used signify" -> "is used to signify" (Bitbake rev: c3dd4fd5c9fe106f7fae8c088e75cfb70f20e107) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: correct typo in ??= documentationDarren Hart2011-04-181-1/+1
| | | | | | | ??= is a lazy version of ?= Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake docs: use dblatex to build the pdf bitbake manualDarren Hart2011-03-161-1/+1
| | | | | | | | | | | | | | Fix [BUGID #593] The current manual build fails for printing formats which use latex as an intermediate format. This bug has been reported in multiple locations and I haven't found a solution posted to any of them. Using --with-dblatex uses dblatex to make the conversion and successfully generates the pdf. It adds a dependency on dblatex and its dependencies. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Joshua Lock <josh@linux.intel.com>
* manual: document scmdata=keep for CVS, SVN and GitAndreas Oberritter2011-01-041-3/+3
| | | | | | | | (Bitbake rev: f42e6d33b986183eee2c74aa7b1bbc9b339276a9) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* *: use print() as a functionBernhard Reutner-Fischer2010-07-161-2/+2
| | | | | | | | | to make python3 happy (Bitbake rev: c82926ccdd4ec4e3ad6e78a381dacb96adf9b409) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fix a couple typos in the CVS Fetcher section.Robert P. J. Day2010-07-021-2/+2
| | | | | | | | | | | "DL_DIRS" -> "DL_DIR" Remove superfluous trailing ">" after CVSDIR. (Bitbake rev: 34f396e749303367e657911bf10c43086dff7552) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bb.event: NotHandled and Handled are on the way outChris Larson2010-07-021-3/+1
| | | | | | | (Bitbake rev: ed35b30f8e09b0bfc15102fa6483c55d6b7d61de) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Implement BBVERSIONSChris Larson2010-03-251-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | This implements a feature similar to BBCLASSEXTEND, but for generating multiple versions of a given recipe. For example: BBVERSIONS = "1.0 2.0 git". In addition to the above, one can utilize [a-b] style patterns, and can have a :<basever> postfix, which allows you to essentially name the range of versions. Both the current version and the basever end up in OVERRIDES, and the basever gets placed into the BPV variable. The default BPV, if none is specified, is the original PV of the recipe, before bbversions processing. In this way, you can do things like: BBVERSIONS = "1.0.[0-6]:1.0.0+ 1.0.[7-9]:1.0.7+" SRC_URI_append_1.0.7+ = "file://some_extra_patch.patch;patch=1" Or you can create a recipe per range, and name the recipe file as such: nano_1.0.7+.bb. (Bitbake rev: 4ee9a56e16f1eb3c1649eaa3127b09ab0e93d1ec) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* usermanual.xml: Add documentation on bblayers.confRichard Purdie2010-03-251-1/+3
| | | | | | (Bitbake rev: 879229d12c2830dba9e0cb794e61e3c698b8dcc7) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Implement ??= operatorChris Larson2010-03-221-1/+7
| | | | | | | | | | | | | | | | | ??= is a lazy, conditional assignment. Whereas a ?= immediately assigns to the variable if the variable has not yet been set, ??= does not apply the default assignment until the end of the parse. As a result, the final ??= for a given variable is used, as opposed to the first as in ?=. Note that the initial implementation relies upon finalise() to apply the defaults, so a "bitbake -e" without specifying a recipe will not show the defaults as set by ??=. Moving application of the default into getVar adds too large a performance hit. We may want to revisit this later. (Bitbake rev: 74f50fbca194c9c72bd2a540f4b9de458cb08e2d) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: usermanual.xml: Add section for ?= var setting.Theodore A. Roth2010-02-101-0/+5
| | | | | | (Bitbake rev: df8309c11a43a9488ca25ec114a2dd3d49b041ff) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Switch to bitbake-dev version (bitbake master upstream)Richard Purdie2010-01-202-20/+12
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Add tryaltconfigs option to disable the alternative configuration ↵Richard Purdie2008-10-281-0/+3
| | | | attempts and make the 'continue' more aggresive
* bitbake: Sync with 1.8 branch upstreamRichard Purdie2008-09-302-6/+8
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5345 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Sync manual updates and version info with bitbake svnRichard Purdie2007-06-121-1/+53
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1920 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Sync with upstream. Richard Purdie2007-01-082-14/+130
| | | | | | | | | | | | | * File licence headers were sanitised causing most of the diff. * cooker.py was created from bin/bitbake. * cvs fetcher port option was added * The -f force option was fixed to work correctly * Multiple entries in rrecrdeps are now handled correctly (allows adding do_deploy to image depends) git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1129 311d38ba-8fff-0310-9ca6-ca027cbcb966
* Fix typoRoss Burton2006-12-051-1/+1
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1005 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Upgrade from 1.4 -> 1.7.4ishRichard Purdie2006-11-161-5/+24
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@863 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Update against upstream stable branch (includes srcdate='now' support)Richard Purdie2006-06-101-4/+4
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@458 311d38ba-8fff-0310-9ca6-ca027cbcb966
* Update to latest bitbakeRichard Purdie2006-03-201-4/+84
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@309 311d38ba-8fff-0310-9ca6-ca027cbcb966
* Update bitbake to latest bitbake svnRichard Purdie2006-02-101-0/+6
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@262 311d38ba-8fff-0310-9ca6-ca027cbcb966
* Initial populationRichard Purdie2005-08-315-0/+1055
git-svn-id: https://svn.o-hand.com/repos/poky@2 311d38ba-8fff-0310-9ca6-ca027cbcb966
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 06:28:57 +0000