summaryrefslogtreecommitdiff
path: root/bitbake/lib/bb/parse/parse_py
AgeCommit message (Collapse)AuthorFiles
2011-02-23bitbake: Remove in-tree versionKhem Raj3
Bitbake should be used by checking it out from its own repo Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-02-22bitbake/BBHandler: Improve handling of multiline comments and warn users of ↵Richard Purdie1
the change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-10BBHandler: remove bb.fetch referrenceYu Ke1
BBHandler.py no longer use bb.fetch, so remove its import statement Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-10parse: pass filename, lineno into the astChris Larson2
We will be needing this information to improve the tracebacks of python code from the metadata, as well as to give the user information about where variables were defined, so they know how it ended up the way it is. (Bitbake rev: 9615c538b894f71a2d1a0ba6b3f260db91e75786) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-04ConfHandler: commentary typo fixesBernhard Reutner-Fischer1
(Bitbake rev: 089dc31932a85455ed0fec8209d0451af4310f94) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04BBHandler: use basename directly in handler()Bernhard Reutner-Fischer1
(Bitbake rev: 739a8ce6ac688061afd55cd3c980d0e9e45c5930) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04BBHandler: use os.path in inherit()Bernhard Reutner-Fischer1
(Bitbake rev: 5b85de2c71973ba490b95a5d9ab634635f395142) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04BBHandler: simplify supports()Bernhard Reutner-Fischer1
(Bitbake rev: 858d704d713d15bf97053eb1374758c74b0d8874) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Switch bitbake internals to use logging directly rather than bb.msgChris Larson2
We use a custom Logger subclass for our loggers This logger provides: - 'debug' method which accepts a debug level - 'plain' method which bypasses log formatting - 'verbose' method which is more detail than info, but less than debug (Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-31bitbake/BBHandler: Save python functions into the dictonaryRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-023.0 prepChris Larson2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02parser: fix harmless typo in variable nameBernhard Reutner-Fischer1
s/absolsute/absolute/ (Bitbake rev: 837c84ce47c298316b941a5f3d2479bd2643686b) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Don't try to expand non-string valuesChris Larson1
(Bitbake rev: fe36a726b9f930bbd6fd758c0aee78559e95f02b) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Move the unset BBPATH sanity check after the bblayers processingChris Larson1
This way we can fully utilize bblayers, you can do everything in bblayers.conf and avoid setting any environment variables at all. (Bitbake rev: 5def1c8c31432968349f9b29d6333d7962260a8b) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Apply some 2to3 transforms that don't cause issues in 2.6Chris Larson2
(Bitbake rev: d39ab776e7ceaefc8361150151cf0892dcb70d9c) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Deprecate the usage of certain objects via certain modulesChris Larson1
As an example, this displays a deprecation warning for the use of "bb.encodeurl" when you should be using "bb.fetch.encodeurl". It includes a convenience function for this purpose. It should be of use when moving objects between modules permanently, changing the API the user sees. (Bitbake rev: 78f56049ba863b2e585b89db12b32697eb879bbc) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Drop __all__ usageChris Larson1
(Bitbake rev: b4983cc7bfe5300c1d2904f34fb03d4fb2f41d90) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Import fixupsChris Larson2
(Bitbake rev: 4fa052f426e3205ebace713eaa22deddc0420e8a) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Formatting cleanupsChris Larson2
(Bitbake rev: 2caf134b43a44dad30af4fbe33033b3c58deee57) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Stop using functions via 'bb' that were moved from there to other modulesChris Larson1
(Bitbake rev: 03a6c26f8da226f442c3cab557e4733f7cd6eeac) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Ensure we always utilize the correct messaging domainsChris Larson1
(Bitbake rev: 92a2e2e90981c0615171abe03645a772d84f6986) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25Implement BBVERSIONSChris Larson1
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>
2010-03-22Fix issues with BBCLASSEXTEND set by anonymous python, and rename some ↵Chris Larson1
variables to improve code clarity (Bitbake rev: 3062e96181fe845cfd286990b0216888ddd3d228) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Implement ??= operatorChris Larson1
??= 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>
2010-03-22Re-getVar BBCLASSEXTEND after finalise()Chris Larson1
This ensures that an anonymous python function is able to manipulate the BBCLASSEXTEND contents, and, therefore, amend.inc files are able to add to it. (Bitbake rev: c7d038d404afaf4ce3735af5134163759da6f6ef) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Error early if BBPATH is unset, rather than falling back to share/bitbakeChris Larson1
Better to error as early as possible rather than experience strange behavior resulting from the use of the largely useless stock bitbake.conf/base.bbclass. (Bitbake rev: 641e6cf3ec3ab4d26929cf4d2a3704ff07eed4d6) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Make resolve_file only resolve the pathHolger Freyther2
Do not attempt to open the file in the resolve_file method (a lot like bb.which... maybe bb.which can be used). This way we don't need to open/close a file which we have already parsed. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Cache parsed .inc and .bbclass files for a parse speedupHolger Freyther1
Have a growing dict with .inc and .bbclass'es. This avoids to reparse files we have already seen. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] prepare to cache some .bbcclass and .inc filesHolger Freyther1
Our parser is shit but instead to replace it now we will see how long we can drive the wave by caching parsed files. This will not go through the feeder again but we can just reevaluate the StatementGroup. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Remove the "data" from feeder, evaluate after parsing a fileHolger Freyther2
Evaluate the statements after having parsed one file. This is referred to as "entwirren" and we can remove the direct evaluation and postpone a bit, in the future we can use a cached copy instead of parsing the original. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parse] Move vars_from_file from bb.parse.BBHandler into bb.parse.Chris Larson1
(Bitbake rev: fda0707d772e0964a0185d4ec4d016522f6972f3) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Add documentation about usage of this codeHolger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Move the finalise into the ast as wellHolger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Cary a Statement Node through the parsingHolger Freyther2
When parsing we will collect a number of statements that can be evaluated...The plan is to be evaluate things twice (old+new) and then compare the result, it should be the same. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Move evaluating into the ast class...Holger Freyther2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: BBHandler: pass lineno and fn to handleMethodKhem Raj1
* lineno and fn are needed in handleMethod to restore the functionality as it was before. (Bitbake rev: ac6792045959cfee56279c1c4597521e990848e7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: parse_py/ConfHandler.py: missing colon after elseMartin Jansa1
(Bitbake rev: d520ae0764016906ff61ec33b14eabc908aa8408) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: ConfHandler: Fix require vs. include behaviourRichard Purdie1
(Bitbake rev: 824a032672c8673cae28e492aa916a4750b94efa) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parser] Move more stuff out the feederHolger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parse] Move inherit handling to methodHolger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parsers] Move out more functionsHolger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parser] Move more stuff out to separate methods...Holger Freyther1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parser] Move the handling of a method to a functionHolger Freyther1
We want to convert this into a proper AST. So move all such operations to methods... Later change them to generate a node... and create that node from here. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parse] Unify opening a file...Holger Freyther2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-10bitbake: [parser] Kill obtain/localpath from the parserHolger Freyther2
With obtain it was possible to use an existing fetcher to download a bb or config file. In practive no one has used it and it was likely broken in regard to depends_cache... Remove it for now, simplfiy the code. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-20bitbake: Switch to bitbake-dev version (bitbake master upstream)Richard Purdie2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-12-18bitbake/BBHandler: Only add do_ prefix to tasks if its not already presentRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-11-13bitbake: Sync various functions with those from bitbake-dev and bitbake upstreamRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-10-13bitbake: Anonymous funciton improvements - use methodpool to allow cached ↵Richard Purdie1
code and remove anonymous function indentation mismatch problems Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2009-10-13bitbake: Remove unused and hence pointless internal__functions__ variableRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-26 18:08:04 +0000