linux/poky.git, branch 1.1_M1.rc1

base.bbclass: use oe.data for OE_IMPORTS

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

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

Shift oe import logic out of the event handler

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

This can be useful if we need the imports from another config parsed event handler, and can't rely upon the base one running before that one. (From OE-Core rev: dc579ce4dcf9a3743ced9eae4fe510a079961faf) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

base.bbclass: switch to current OE's imports handling

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

The current mechanism makes it easier for classes to add new oe modules to be automatically imported, and thereby made available to python snippets (${@}). (From OE-Core rev: 0c560a2a7954412f714db86b1aaadb7acbe72d1b) Signed-off-by: Chris Larson 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

kernel.bbclass: pass KERNEL_VERSION through legitimize_package_name

2011-05-20T16:30:49+00:00

- KERNEL_VERSION may contain characters unsuitable for package names, e.g. underscores. Use legitimize_package_name to replace those characters. (From OE-Core rev: 8c6bf9f6775fc5aaa8bc2c77924c95a00f1c1890) Signed-off-by: Andreas Oberritter Signed-off-by: Richard Purdie

Revert "u-boot: fix LIC_FILE_CHKSUM"

2011-05-20T16:08:51+00:00

This reverts commit 2d2563a7b003b265b5cdad98588606379e5edd4c. Saul discovered this change was incorrect.

ed (GPLv2): remove --disable-silent-rules

2011-05-20T11:44:31+00:00

Older version of configure in ed does not like this option, so remove it from CONFIGUREOPTS (From OE-Core rev: bc1a87f3806e021e868bf455a342fccf97a7394d) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

modutils-cross: fix install issue

2011-05-20T11:43:32+00:00

[YOCTO #1055] (From OE-Core rev: 9304a42711c04fa0b496595a6abaad8b7e33c923) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

tcmode-default: switch to gcc 4.6.0 for x86, x86-64 & arm

2011-05-20T11:40:45+00:00

mips & ppc are not ready yet. Waiting for kernel issues to be fixed. (From OE-Core rev: c36623f4906633e186411ed973ea8d41d227e4c3) Signed-off-by: Nitin A Kamble Signed-off-by: Richard Purdie