summaryrefslogtreecommitdiff
path: root/bitbake
Commit message (Collapse)AuthorAgeFilesLines
* utils: improve wording of error messageBernhard Reutner-Fischer2010-03-251-1/+1
| | | | | | | | (Bitbake rev: b2486ec57c6a7adf09d0960fdf6727881b324d2f) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Gross hack to fix packaged-staging with BBCLASSEXTEND packagesRichard Purdie2010-03-231-0/+2
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/cooker.py: Add support for a bblayers.conf fileRichard Purdie2010-03-221-8/+25
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/providers: Fix merge errorRichard Purdie2010-03-221-3/+3
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* cooker: bail out early if no files to buildBernhard Reutner-Fischer2010-03-221-1/+2
| | | | | | | | | | | | | | | | | | | This prevents a misleading backtrace: ERROR: no files to build. Command execution failed: Traceback (most recent call last): File ".../bitbake/build/lib/bb/command.py", line 83, in runAsyncCommand self.cooker.updateCache() File ".../bitbake/build/lib/bb/cooker.py", line 779, in updateCache if not self.parser.parse_next(): File ".../bitbake/build/lib/bb/cooker.py", line 969, in parse_next cooker.bb_cache.sync() UnboundLocalError: local variable 'cooker' referenced before assignment (Bitbake rev: 060ef3d957615b7eb1209dc0d01ebeb53f8c4edc) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fix issues with BBCLASSEXTEND set by anonymous python, and rename some ↵Chris Larson2010-03-221-14/+16
| | | | | | | | | 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>
* Implement ??= operatorChris Larson2010-03-223-2/+19
| | | | | | | | | | | | | | | | | ??= 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>
* Avoid unnecessary calls to keys() when iterating over dictionaries.Chris Larson2010-03-226-30/+21
| | | | | | | | | | | | | | | | | | dict objects provide an __iter__ method for the iteration which gives you the keys, so calling keys directly is unnecessary, and isn't really a best practice. The only time you really need to call the keys is if there's a danger of the dict changing out from underneith you, either due to external forces or due to modification of the iterable in the loop. Iterations over os.environ are apparently subject to such changes, so they must continue to use keys(). As an aside, also switches a couple spots to using sorted() rather than creating a temporary list with keys() and sorting that. (Bitbake rev: 5b6ccb16c6e71e23dac6920cd2df994d67c2587b) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* knotty: tweak failure phraseBernhard Reutner-Fischer2010-03-221-1/+1
| | | | | | | | | | ..to make copy and paste of the logfile easier. (Bitbake rev: 446cc0cebd4daff7f849717f4cb89ac1b4c6b755) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fix ud.basecmd error introduced by the FETCHCMD_git commitChris Larson2010-03-221-1/+2
| | | | | | | (Bitbake rev: 0bbcbe3548f39ca46c5aa3bf1a8681026e51cbf0) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Add initial 'repo' fetcherTom Rini2010-03-222-0/+108
| | | | | | | | (Bitbake rev: f68406e864c9837feb56cbec993b620481445cc2) Signed-off-by: Tom Rini <tom_rini@mentor.com> Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Re-getVar BBCLASSEXTEND after finalise()Chris Larson2010-03-221-3/+2
| | | | | | | | | | 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>
* Error early if BBPATH is unset, rather than falling back to share/bitbakeChris Larson2010-03-221-5/+1
| | | | | | | | | | 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>
* Kill unused projectdir in bb package.Chris Larson2010-03-221-12/+1
| | | | | | | (Bitbake rev: 79b93e6929c5feeb1ad05bd17f589c69f00b77f6) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fix msg usage in the moved utility functions.Chris Larson2010-03-221-15/+15
| | | | | | | (Bitbake rev: 686288444d22091dee66e20ec49b9c53f8c980b7) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move most utility functions from bb into bb.utils.Chris Larson2010-03-222-909/+764
| | | | | | | (Bitbake rev: ff720ec59b30671c951dbf3b96df10ef56b8b505) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move compat imports in the bb package to avoid circular dep issues.Chris Larson2010-03-221-5/+4
| | | | | | | (Bitbake rev: b66c129edc7d78fed9d41b0c634744ec81931b21) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move encodeurl, decodeurl into bb.fetch.Chris Larson2010-03-222-108/+95
| | | | | | | (Bitbake rev: 867d36f9afce2d298874ac7563e5b3852ef04659) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move MalformedUrl, VarExpandError into appropriate modules.Chris Larson2010-03-223-5/+9
| | | | | | | (Bitbake rev: e616483b237dafff7f90ba1c09e9ee7c383a2e47) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Add FETCHCMD parameter for gitMartyn Welch2010-03-221-10/+13
| | | | | | | | | | | | | | | The Git fetcher currently hardwires the git command to "git". Allow the path and any additional wrappers to the Git command to be provided via FETCHCMD functionality, as with some of the other fetchers. If FETCHCMD_git is not define in bitbake.conf, the fetcher defaults to "git". (Bitbake rev: f3afb79ecac30d973a3c62ff6baf28d8b7388a24) Signed-off-by: Malcolm Crossley <malcolm.crossley@ge.com> Signed-off-by: Martyn Welch <martyn.welch@ge.com> Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake fetch/__init__.py: Failing urls should raise errors, not fatal ↵Richard Purdie2010-03-151-1/+1
| | | | | | exceptions Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Revert "providers.py: sort eligible providers by DEFAULT_PREFERENCE"Richard Purdie2010-02-161-2/+0
| | | | | | | | This breaks preferred providers functionality This reverts commit ee9afccf33b220a21b74fab279925eeb4771249b. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [cache] copy instead of deepcopy in syncHolger Freyther2010-02-151-1/+1
| | | | | | | We only intend to modify the dict, no need to copy all elements. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parse] In ast, make StatementGroup inherit list, and add a AstNode ↵Chris Larson2010-02-151-22/+13
| | | | | | | | | base class. (Bitbake rev: 7ea31b2842b45ffe1ca688f55207f8676442a108) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parse] Use bb.which in resolve_fileChris Larson2010-02-151-7/+3
| | | | | | | (Bitbake rev: 3cd06ed487ee0617892f154cff461379a323a1fb) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Make resolve_file only resolve the pathHolger Freyther2010-02-153-16/+12
| | | | | | | | 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>
* bitbake: [parser] Cache parsed .inc and .bbclass files for a parse speedupHolger Freyther2010-02-151-14/+23
| | | | | | | 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>
* bitbake: [parser] prepare to cache some .bbcclass and .inc filesHolger Freyther2010-02-151-11/+18
| | | | | | | | | 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>
* bitbake: [parser] Remove the "data" from feeder, evaluate after parsing a fileHolger Freyther2010-02-154-64/+51
| | | | | | | | | 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>
* bitbake: [parse] Move vars_from_file from bb.parse.BBHandler into bb.parse.Chris Larson2010-02-152-21/+23
| | | | | | | (Bitbake rev: fda0707d772e0964a0185d4ec4d016522f6972f3) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parse] Don't use relative import of parse_py.Chris Larson2010-02-151-1/+1
| | | | | | | (Bitbake rev: 0a2bb3dd790e3e40867195f14f4e174f98f8a47c) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parse] Move the last method to the AST...Holger Freyther2010-02-151-1/+10
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Move more methods to the ast schemeHolger Freyther2010-02-151-31/+48
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Move one more item to the astHolger Freyther2010-02-151-34/+41
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Move methodflags over to the astHolger Freyther2010-02-151-15/+23
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Build fixRichard Purdie2010-02-151-2/+2
| | | | | | (Bitbake rev: 9c97696f37499b4d0ec5c034c51e4cf6bc425ba2) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Move more statements over the two phase ASTHolger Freyther2010-02-151-17/+40
| | | | | | Create the data first, then evaluate on the data dict Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parse] Change handling include through the AstNodeHolger Freyther2010-02-151-8/+2
| | | | | | | Disable the recursively evaluating the statement for now as it is causing problems. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Call eval and remove non ast codeHolger Freyther2010-02-151-2/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Call eval immeditaley to test this codeHolger Freyther2010-02-151-33/+4
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Prepare to cease out getFuncHolger Freyther2010-02-151-12/+17
| | | | | | | getFunc is now a method of the data node, hopefully we can kill the other version soon. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Preserve include vs. require behaviourRichard Purdie2010-02-151-3/+7
| | | | | | (Bitbake rev: 6073a5b8e4ca8af8e1a8e0234fad7b08baf76c99) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Firs set of AST nodes with construction and evalHolger Freyther2010-02-151-0/+78
| | | | | | | | First set of ConfHandling with AST nodes. The include can use a speed up and things might need to be migrated... into this class. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Add documentation about usage of this codeHolger Freyther2010-02-151-0/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Move the finalise into the ast as wellHolger Freyther2010-02-152-43/+41
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: [parser] Cary a Statement Node through the parsingHolger Freyther2010-02-154-79/+92
| | | | | | | | | 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>
* bitbake: [parser] Move evaluating into the ast class...Holger Freyther2010-02-153-180/+207
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: providers.py: sort eligible providers by DEFAULT_PREFERENCEBernhard Reutner-Fischer2010-02-151-0/+2
| | | | | | | (Bitbake rev: ee9afccf33b220a21b74fab279925eeb4771249b) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: runqueue.py: improve printing dependent tasksBernhard Reutner-Fischer2010-02-151-2/+10
| | | | | | | | | | | | | | | | | Print names instead of Task-IDs (and not mentioning they're task ids). Previously we printed e.g.: Dependency loop #1 found: Task 89 (/there/src/oe/openembedded/recipes/busybox/busybox-native_1.15.2.bb, do_configure) (depends: Set([88, 282, 92, 87])) Now we say Dependency loop #1 found: Task 89 (/there/src/oe/openembedded/recipes/busybox/busybox-native_1.15.2.bb, do_configure) (dependent Task-IDs ['busybox-native, do_patch', 'update-rc.d, do_populate_staging', 'busybox-native, do_populate_staging', 'shasum-native.bb, do_populate_staging', 'busybox-native, do_unpack']) (Bitbake rev: 00eaf76fdc32eb515995b47dfa69eb90ca904b37) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: taskdata.py: fix typo in debug messageBernhard Reutner-Fischer2010-02-151-1/+1
| | | | | | | (Bitbake rev: 457fb59f10ed59269b8bda3ee53bbeded5d33eb5) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-09 00:08:34 +0000