| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
to make python3 happy
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
|
|
"DL_DIRS" -> "DL_DIR"
Remove superfluous trailing ">" after CVSDIR.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
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.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
??= 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.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
|
|
|
|
the patch)
|
|
|
|
|
|
|
|
Patch courtsey Justin Patrin to teach BitBake SRCDATE="now" handling.
If SRCDATE is set to now we will not look at the temporary DL_DIR
for a saved tarball as we want to download a new version. OpenEmbedded
should consider stamping the do fetch phase.
Justin thanks for the patch and sorry for all the trouble
bitbake/doc/manual/usermanual.xml: Document the 'now' method for svn,svk and cvs
|
|
The CreateCommons license is now at version 2.5. The spirit
remains unchanged.
|
|
Start documenting the -g option... well start with it. Hopefully
someone else will document it.
|
|
|
|
The python method needs a closing brace. Add the
missing one.
|
|
Start documenting the available fetchers and their VARIABLES
and Parameters
|
|
As pointed out by a monkey on irc we have a copy
and paste error in the example for the =. and .=
operator.
Hopefully this fixes this issue
|
|
-Mention the new require keyword
|
|
-Update the result of bitbake --help
-Add note of the removal of bbread and its replacement with bitbake -e
|
|
-Provide an example for writing an event handler
|
|
-Update 1 to True to catch up with python 2.2 ;)
|
|
-Add Documentation for the .= and =. operators we introduce
with Bitbake 1.3.2.
|
|
|
|
example usage of bbfile collections.
|
|
|
|
|
|
|
Andreas Oberritter
Bernhard Reutner-Fischer
Robert P. J. Day
Chris Larson
Richard Purdie
Theodore A. Roth
Holger Hans Peter Freyther
Chris Larson