linux/poky.git/bitbake/lib/bb/parse/parse_py, branch 1.3_M3.rc2

BBHandler: Tweak some data store access methods to the preferred syntax

2012-05-25T10:15:11+00:00

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

ConfHandler.py: Add a hook for config parsing

2012-04-13T11:04:18+00:00

To make the UI settings take effect, we need to hook at the end of each config file parsing and set UI specific values. (Bitbake rev: f54e733c7863110896f43900d9e4e791602f9d65) Signed-off-by: Richard Purdie Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

parse/ast: Expand inherit statements before splitting them

2012-03-15T22:56:16+00:00

This means that statements that expand to more then one entry such as: CLASSES = "a b" inherit ${CLASSES} work correctly instead of trying to inherit a class called "a b". (Bitbake rev: 2568e9ace6e6f483e1bf2a9ef2f4d8318d6c85b7) Signed-off-by: Richard Purdie

meta/classes: Convert to use appendVar and appendVarFlags

2012-03-05T18:36:53+00:00

(From OE-Core rev: 3b57de68e70e77dbc03c0616a83a29a2e99e40b4) Signed-off-by: Richard Purdie

parse/ConfHandler: Fix enthusiatic export regexp matching

2012-02-29T13:12:12+00:00

The export regexp was only meant to catch values like: export VARIABLENAME however after the stricter quoting patch was applied, it was also matching variables like: export BAR=foo and setting the export flag on a variable called "BAR=foo". The = character is an invalid variable name character. This patch tightens up the regexp match so it only matches the intended character set and only matches variable names. (Bitbake rev: 6d1765c2eac8c1958ceb9c81d55d04a9bc961cb1) Signed-off-by: Richard Purdie

bitbake/ConfHandler: Be more strict about variable quoting

2012-02-28T12:33:20+00:00

Currently, bitbake will accept variables in the forms: X = 1 X = '1 \ X = "1" X = '1' which will all set X=1. This patch removes the first two possibilities and makes quoting mandatory. There is little metadata out there which doesn't quote properly and bitbake will exit with an error about the exact line number and file with any problem so users can easily identify and fix issues. OE-Core has already been checked/fixed. The motivation for this is being able to give sane errors if a user does something like: IMAGE_INSTALL += # tslib mtd-utils" which currently gives a really nasty failure. (Bitbake rev: a8ae80741fea5e0ec0fb9a52a963a4baa38d2564) Signed-off-by: Richard Purdie

bitbake: add file and line number to ParseError

2012-02-23T22:52:15+00:00

Ensure that a file and line number are reported for ParseError where possible. This helps particularly in the case of inherit and require which previously did not report either of these upon failure. (Bitbake rev: f588ba69622a2df35417ced184e56c79ac1b40d5) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

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

parse_py: Use absolute paths for FILE

2011-11-18T14:22:40+00:00

Its possible for relative paths to creep into FILE. These confuse the build system no end as its not clear where they might be releative to. This patch ensures we always use resolved absolute paths for FILE so that things behave in a deterministic way. (Bitbake rev: 658d7daa70e46c2b20973b90ee53f0bbadc8bf5d) Signed-off-by: Richard Purdie

Fix typos in local.conf.sample and local.conf.sample.extended

2011-10-11T13:11:30+00:00

Fixes bug [YOCTO #1667] Fix typos in local.conf.sample and local.conf.sample.extended: differernt -> different chages -> changes complation -> compilation egde -> edge "an an" -> "as an" images's -> image's Signed-off-by: Robert Yang Signed-off-by: Richard Purdie