linux/poky.git/bitbake, branch 1.3_beta

bitbake: ast: Store anonymous python function contents in the datstore

2012-08-23T08:22:44+00:00

This is useful if we need to disable part of one during a backtrace for debugging purposes. (Bitbake rev: 80a0c1b06a30a6ba9977c29fac0437a208d8cbbc) Signed-off-by: Richard Purdie

bitbake: ast: Extract text variable in PythonMethodNode

2012-08-23T08:22:44+00:00

(Bitbake rev: 2e98f740b4a57a3467b1a00b1ebc1aaee33a8ff0) Signed-off-by: Richard Purdie

bitbake: ast: Rename PythonMethodNode define variable to modulename

2012-08-23T08:22:44+00:00

It was hard for me to understand what the define variable was, modulename is hopefully a bit better. (Bitbake rev: 79f9f46319de85f85613ebe248c327f5852225ba) Signed-off-by: Richard Purdie

bitbake: methodpool: Clean up the parsed module list handling to be slightly less insane

2012-08-23T08:22:44+00:00

This removes some dubious functions and replaces them with a simpler, cleaner API which better describes what the code is doing. Unused code/variables are removed and comments tweaked. (Bitbake rev: f1e943aebfb84e98253f3f21646d6765c4fa1d66) Signed-off-by: Richard Purdie

bitbake: methodpool: Remove unused check_insert_method function

2012-08-23T08:22:43+00:00

(Bitbake rev: 4664333e55ffc9d618f2c2f074200923209fd6c4) Signed-off-by: Richard Purdie

bitbake: cooker: Add explict handling of BBHandledException for parsing failures

2012-08-23T08:22:43+00:00

This removes some unnecessary tracebacks (Bitbake rev: db0ff7b4d47fce8322dd2350a2b1a6f60ef61d25) Signed-off-by: Richard Purdie

bitbake: cooker: Ensure parsing failures stop the build

2012-08-23T08:22:43+00:00

Currently parsing failures still allow bitbake to continue on and try and execute a build. This is clearly a bad idea and this patch adds in more correct error handling and stops the build. The use of sys.exit is nasty but this patches other usage in this function so is at least consisent and its better than the current situation of trying to execure a half parsed set of recipes. There are probably better ways this could be improved to use to stop the build. (Bitbake rev: 22756e9c0f1da33ba2c6e881b214577a610b7986) Signed-off-by: Richard Purdie

bitbake: utils.py: Once we've printed errors messages, suppress the backtrace

2012-08-23T08:22:42+00:00

Adding a generic backtrace to better_compile and better_exec is pointless, therefore reraise the exception as a bb.BBHandledException so the generic code doesn't confuse the user even more. (Bitbake rev: b3d97130e1e70fe969399277dcd7cccd888103d6) Signed-off-by: Richard Purdie

bitbake: utils.py: Try harder to extract good traceback information by querying the datastore

2012-08-23T08:22:42+00:00

Currently as soon as execution passes outside the code fragment being executed by better_exec, we don't get any good traceback information, just a likely obscure reference to some function name which may or may not be identifiable. This patch adds code to query the datastore if present, allowing a more meaningful back trace to be displayed in many cases. [YOCTO #2981] (Bitbake rev: 0edf8431f9ff52581afe0d3ef525c59909af02ba) Signed-off-by: Richard Purdie

bitbake: cooker: fix traceback when using -b with skipped recipe

2012-08-23T08:22:42+00:00

If a recipe is skipped during parsing for whatever reason, check and report this as an error rather than trying to use the data that is sent back and failing. Fixes [YOCTO #2976]. (Bitbake rev: a324df40243fa55ccc89fd5970d46f25330d0a0d) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie