| Age | Commit message (Collapse) | Author |
|---|
|
Even if there are not so many users of base.bbclass bundled in bitbake,
it is helpful as sample code at least.
If this base.bbclass is used, bitbake emits the following warnings:
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 41
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 42
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 43
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 44
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 45
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 46
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 47
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 53
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 54
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 55
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 56
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 63
WARNING: python should use 4 spaces indentation, but found tabs in base.bbclass, line 64
Let's fix the indentation as suggested. While I was touching these lines,
I also fixed "isnt" into "isn't" in the comment line.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
getVar() has been defaulting to expanding by default for
a long time (2016), thus remove the True option from
getVar() calls with a regex search and replace.
Search & replace made using the following command:
sed -e 's|\(d\.getVar \?\)( \?\([^,()]*\), \?True)|\1(\2)|g' \
-i $(git grep -E 'getVar ?\( ?([^,()]*), ?True\)' \
| cut -d':' -f1 \
| sort -u)
Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
[YOCTO #9603]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Patch from Andrew Stubbs <ams@codesourcery.com> to fix listtasks and showdata
functions to output data correctly.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Using "1" with getVar is bad coding style and "True" is preferred.
This patch is a sed over bitbake directory of the form:
sed \
-e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \
-e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \
-i `grep -ril getVar *`
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
We use a custom Logger subclass for our loggers
This logger provides:
- 'debug' method which accepts a debug level
- 'plain' method which bypasses log formatting
- 'verbose' method which is more detail than info, but less than debug
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
I could argue in favor of the removal of these entirely, as their usefulness
is limited, and I've yet to see anyone use bitbake for anything without using
OE as a base. It's something to consider, anyway, but this at least makes
them parse without complaining.
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
bitbake/lib/bb/build.py:
bitbake/lib/bb/utils.py:
bitbake/lib/bb/shell.py:
bitbake/lib/bb/providers.py:
bitbake/lib/bb/msg.py:
bitbake/bin/bitbake:
bitbake/bin/bitdoc:
bitbake/classes/base.bbclass:
Start an overhaul of the message handling in bitbake:
- Introduce a new msg module to replace the existing simple calls.
- The msg module adds the conncept of message domains so ultimately we can
select which kinds of debug messages we want to see (it uses an Enum class
for this)
- Add a warn logging level for things the user should really pay attention to
as note is a little overloaded at present
- Start converting to use the new fuctions
|
|
-bb.data is now a delegate to hookable Data implementation.
-bb.data.init() is the 'factory' method to create a instance
of a concrete implementation.
-Kill assumptions that bb.data.init() returns a {} (python dict)
-Add the old Dictionary Based Implementation as data_dict.py
|
|
|
|
|
Masahiro Yamada
André Draszik
Richard Purdie
Chris Larson
Chris Larson
Richard Purdie
Holger Hans Peter Freyther
Chris Larson