linux/poky.git/meta/lib/oe/data.py, branch 1.4_M6.rc1

Remove a number of unneeded import os/bb calls

2012-07-19T11:24:50+00:00

The bb and os modules are always imported so having these extra import calls are a waste of space/execution time. They also set a bad example for people copy and pasting code so clean them up. (From OE-Core rev: 7d674820958be3a7051ea619effe1a6061d9cbe2) Signed-off-by: Richard Purdie

meta: Replace bb.data.expand(xxx, d) -> d.expand(xxx)

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

sed \ -e 's:bb.data.$expand([^,()]*$, *$[^) ]*$ *):\2.\1):g' \ -i `grep -ril bb.data.expand *` Signed-off-by: Richard Purdie

data.py: fixed message domain errors

2011-10-14T13:36:58+00:00

The dynamic message domain was introduced by Richard Purdie with the following patch: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a6c48298b17e6a5844b3638b422fe226e3b67b89 (From OE-Core rev: 55a8382e460430dc5ff10755d235d637531d2ae7) Signed-off-by: Samuel Stirtzel Signed-off-by: Richard Purdie

oe.data: expand the flags

2011-05-20T16:34:22+00:00

(From OE-Core rev: 8b9de6d2ad2d351bbc288cbb12562806ba8edae2) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Implement variable typing (sync from OE)

2011-05-20T16:34:22+00:00

This implementation consists of two components: - Type creation python modules, whose job it is to construct objects of the defined type for a given variable in the metadata - typecheck.bbclass, which iterates over all configuration variables with a type defined and uses oe.types to check the validity of the values This gives us a few benefits: - Automatic sanity checking of all configuration variables with a defined type - Avoid duplicating the "how do I make use of the value of this variable" logic between its users. For variables like PATH, this is simply a split(), for boolean variables, the duplication can result in confusing, or even mismatched semantics (is this 0/1, empty/nonempty, what?) - Make it easier to create a configuration UI, as the type information could be used to provide a better interface than a text edit box (e.g checkbox for 'boolean', dropdown for 'choice') This functionality is entirely opt-in right now. To enable the configuration variable type checking, simply INHERIT += "typecheck". Example of a failing type check: BAZ = "foo" BAZ[type] = "boolean" $ bitbake -p FATAL: BAZ: Invalid boolean value 'foo' $ Examples of leveraging oe.types in a python snippet: PACKAGES[type] = "list" python () { import oe.data for pkg in oe.data.typed_value("PACKAGES", d): bb.note("package: %s" % pkg) } LIBTOOL_HAS_SYSROOT = "yes" LIBTOOL_HAS_SYSROOT[type] = "boolean" python () { import oe.data assert(oe.data.typed_value("LIBTOOL_HAS_SYSROOT", d) == True) } (From OE-Core rev: a04ce490e933fc7534db33f635b025c25329c564) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie