summaryrefslogtreecommitdiff
path: root/bitbake
AgeCommit message (Collapse)AuthorFiles
2010-06-30bitbake: Add bb.utils.join_deps to handle creation of dependency strings ↵Richard Purdie1
with versions Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-29bitbake: create cooker object after cleaning the environmentJeff Dike1
Previously, the cooker object was created before the environment was cleaned, saving everything that was in the environment and dumping into the run scripts. The patch ensures that the cooker gets a cleaned environment when it's created. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-29bitbake: Move the logger initialization from cooker to utilsJeff Dike3
In order to move the environment cleaning, which wants to log a message, before cooker creation, the logging facility initialization needs to happen earlier. So, it is now in init_logger in utils.py and called from bitbake before the creation of the data object. It also seems more correct to initialize a global facility like this from a more global context than the creation of an object, of which there could theoretically be many. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-25bitbake: allow fakeroot functionality to be provided by an alternative programJoshua Lock1
If the variable FAKEROOT is set its value will be used, otherwise we default to fakeroot. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-06-07bitbake decodeurl: fix the file:// url handlingNitin A Kamble1
Without this patch decoding a url of this kind file://dir/filename gives path=/filename host=dir. With the patch it decodes as path=/dir/filename host="" Probably nobody stumbled on this issue yet because nobody used file:// urls with directory names in the path. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2010-03-25bitbake/event.py: Run class eventhandlers in the task context but ensure UI ↵Richard Purdie1
handlers run in the server context Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bitbake/cooker.py: Finishing the command needs to happen after the ↵Richard Purdie1
BuildCompleted event else the cooker can shutdown first Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25cache.py: Bump the cache version after the BBVERSIONS updateRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bb.manifest: Drop, its unused and obsolete. No point in having dead code aroundRichard Purdie1
(Bitbake rev: 69374497b557a5e99ffc7cbe5e075d63e2d9cfaa) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25BBFILES: use a set to remove duplicates when collecting.Chris Larson1
(Bitbake rev: b1b06133da4ca379a60775552d481f7fbf77e999) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bb/command was importing bb and accessing some of its own classes indirectly ↵Chris Larson1
as bb.command.<class> (Bitbake rev: 4b2a268ce8dad63d21619c1b9acc1de86d222d93) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25Why is bb/__init__.py importing bb?Chris Larson1
(Bitbake rev: 3eb01a20cbbb2e7a2f6278089bcc9bb70021738f) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25data_smart: be explicit about what we make available to eval'd python codeChris Larson1
(Bitbake rev: 6a73dda60f50e9b3e5513795d1ec7207d1446de2) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25Fix 7 references to undefined variables, as spotted by pyflakesChris Larson4
(Bitbake rev: e1e4ccf203e38070eeafd31a622671996cff61a1) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bb.utils: remove old portage remnantsChris Larson2
The following utility functions were removed. Note that in this particular case we're bypassing a proper deprecation process, as these functions are clearly not utilized, are obvious remnants of old ways of doing things, and some of which do not even function properly. - tokenize - evaluate - flatten - relparse - ververify - isjustname - isspecific - catpkgsplit - pkgsplit - pkgcmp - dep_parenreduce - dep_opconvert (Bitbake rev: 62983ad9b151ee8d51e8cf9a31c736c7813edf16) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bb.utils: utilize string.letters and string.digitsChris Larson1
(Bitbake rev: 7af05cba87ec9f3ea5e53689b3d9f0a63784d1b5) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25bb.which: fix broken direction/reverse argumentChris Larson1
(Bitbake rev: 4725d83f532cad96168aa9affdedb33b6fc897b7) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25crumbs: fix hassattr typoChris Larson1
(Bitbake rev: 5593de13a18792e36d15dfd2a9579b36284e4d67) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25Implement BBVERSIONSChris Larson4
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-25usermanual.xml: Add documentation on bblayers.confRichard Purdie1
(Bitbake rev: 879229d12c2830dba9e0cb794e61e3c698b8dcc7) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25Expand PREMIRRORSEnrico Scholz1
When not expanding PREMIRRORS, the functions fails/does not work correctly when PREMIRRORS is not a plain string (e.g. contains ${...} or a ${@...} statements). (Bitbake rev: d612d22b073f68b8cf1bb7344e0487820040d80d) Signed-off-by: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-25utils: improve wording of error messageBernhard Reutner-Fischer1
(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>
2010-03-23bitbake: Gross hack to fix packaged-staging with BBCLASSEXTEND packagesRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22bitbake/cooker.py: Add support for a bblayers.conf fileRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22bitbake/providers: Fix merge errorRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22cooker: bail out early if no files to buildBernhard Reutner-Fischer1
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>
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 Larson3
??= 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-22Avoid unnecessary calls to keys() when iterating over dictionaries.Chris Larson6
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>
2010-03-22knotty: tweak failure phraseBernhard Reutner-Fischer1
..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>
2010-03-22Fix ud.basecmd error introduced by the FETCHCMD_git commitChris Larson1
(Bitbake rev: 0bbcbe3548f39ca46c5aa3bf1a8681026e51cbf0) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Add initial 'repo' fetcherTom Rini2
(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>
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-03-22Kill unused projectdir in bb package.Chris Larson1
(Bitbake rev: 79b93e6929c5feeb1ad05bd17f589c69f00b77f6) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Fix msg usage in the moved utility functions.Chris Larson1
(Bitbake rev: 686288444d22091dee66e20ec49b9c53f8c980b7) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Move most utility functions from bb into bb.utils.Chris Larson2
(Bitbake rev: ff720ec59b30671c951dbf3b96df10ef56b8b505) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Move compat imports in the bb package to avoid circular dep issues.Chris Larson1
(Bitbake rev: b66c129edc7d78fed9d41b0c634744ec81931b21) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Move encodeurl, decodeurl into bb.fetch.Chris Larson2
(Bitbake rev: 867d36f9afce2d298874ac7563e5b3852ef04659) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Move MalformedUrl, VarExpandError into appropriate modules.Chris Larson3
(Bitbake rev: e616483b237dafff7f90ba1c09e9ee7c383a2e47) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-03-22Add FETCHCMD parameter for gitMartyn Welch1
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>
2010-03-15bitbake fetch/__init__.py: Failing urls should raise errors, not fatal ↵Richard Purdie1
exceptions Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-16bitbake: Revert "providers.py: sort eligible providers by DEFAULT_PREFERENCE"Richard Purdie1
This breaks preferred providers functionality This reverts commit ee9afccf33b220a21b74fab279925eeb4771249b. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [cache] copy instead of deepcopy in syncHolger Freyther1
We only intend to modify the dict, no need to copy all elements. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parse] In ast, make StatementGroup inherit list, and add a AstNode ↵Chris Larson1
base class. (Bitbake rev: 7ea31b2842b45ffe1ca688f55207f8676442a108) Signed-off-by: Chris Larson <clarson@mvista.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parse] Use bb.which in resolve_fileChris Larson1
(Bitbake rev: 3cd06ed487ee0617892f154cff461379a323a1fb) Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-02-15bitbake: [parser] Make resolve_file only resolve the pathHolger Freyther3
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 Freyther4
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-24 17:02:48 +0000