linux/poky.git/bitbake/lib/bb/parse/ast.py, branch 1.2_M2.rc1

bitbake: Update users of getVar/setVar to use the data store functions directly

2011-11-27T10:35:30+00:00

Signed-off-by: Richard Purdie

bitbake/ast: include class name when arguments given in variant

2011-07-25T11:09:40+00:00

For multilib this produces variants of e.g. "multilib:lib64" instead of just "lib64"; however we set BBEXTENDVARIANT to "lib64" and the latter will be used when composing filenames for multilib. (Bitbake rev: de7a2b91512bb3ab058f5eb5cd188acd2b8a2220) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake/ast: Fix ??= vs. ?= handling

2011-07-05T10:39:05+00:00

As the code stands, setting a variable with ??= could result in a ?= variable not overriding it. This patch fixes the issue by allowing the ast to make lookups that ignore any ??= set variables. (Bitbake rev: 32fee2e650dfdd3aa9a7572dad1251e0c24ca34b) Signed-off-by: Richard Purdie

bitbake/ast: Add optional argument for BBCLASSEXTEND

2011-06-28T14:27:43+00:00

Add an optional argument to BBCLASSEXTEND entries which gets passed to the extention class as BBEXTENDVARIANT. Also add BBEXTENDCURR whic is set to the current extension class name. This mode functions slightly differently to the previous BBCLASSEXTEND code in that PN is not changed. (Bitbake rev: 8d3c899e0a15840c54de26d2f1fc552430517778) Signed-off-by: Richard Purdie

bitbake/ast: Call expandkeys after the RecipePreFinalise event

2011-06-28T14:27:42+00:00

This means the event handler can change variables such as PN and those changes will be reflected in the updated variable key names. (Bitbake rev: 664b85742d1afc94b291a85fd245abebffacdf3d) Signed-off-by: Richard Purdie

bitbake/event/ast: Add RecipePreFinalise event

2011-06-09T21:43:46+00:00

One of the implications is we need to register the event handlers before executing the anonymous python functions. I can't find any issue with making that change in any existing metadata use cases. (Bitbake rev: a981df3cc9bf410d24f39919959952bdc6c76d03) Signed-off-by: Richard Purdie

bitbake/parse/ast: We always need to finalize the default data since otherwise overrides to BBCLASSEXTEND may not be applied

2011-06-09T21:43:45+00:00

(Bitbake rev: f22ac9149cc9ab96510bb377deb82cd9bceb95c1) Signed-off-by: Richard Purdie

track skipped packages

2011-06-09T17:12:51+00:00

Add skiplist to cooker that allows access to the list of packages skipped via SkipPackage (this includes COMPATIBLE_MACHINE, INCOMPATIBLE_LICENSE, etc.) This can be used to enhance error reporting. (From Poky rev: 6c12b7b1099c77b87d4431d55e949cf7c5f52ded) (Bitbake rev: 7d2363f35350be27a33f568c23eb07fcd3d27e53) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

parse: pass a useful (if mangled) key to bb.data.expand for :=

2011-06-07T21:29:25+00:00

(Bitbake rev: 8e1be0ca414d9d26e013ae212abdd9c39fa8df26) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bitbake/ast.py: Only run finalise() for the specified variant

2011-05-05T14:52:36+00:00

Allows the heavy finalise function to only be run for the case we're interested in when running tasks, saving some processing time. Signed-off-by: Richard Purdie