aboutsummaryrefslogtreecommitdiffstats
path: root/classes/base.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* base.bbclass: fix 'python should use 4 spaces indentation' warningsMasahiro Yamada2019-12-281-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* bitbake: remove True option to getVar callsAndré Draszik2019-02-121-1/+1
| | | | | | | | | | | | | | | 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>
* classes/base.bbclass: Fix missing getVarFlag parameterRichard Purdie2016-05-241-2/+2
| | | | | | [YOCTO #9603] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Fix bitbake example class usageRichard Purdie2013-01-181-2/+2
| | | | | | | 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>
* bitbake: Convert getVar/getVarFlag(xxx, 1) -> (xxx, True)Richard Purdie2012-03-031-1/+1
| | | | | | | | | | | | | 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>
* conf/classes: Catch up with bb.data -> direct object access conversionRichard Purdie2012-03-031-3/+3
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Switch bitbake internals to use logging directly rather than bb.msgChris Larson2010-09-031-12/+0
| | | | | | | | | | | 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>
* Update the minimal base.bbclass & bitbake.conf.Chris Larson2009-07-231-1/+1
| | | | | | | | | 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/__init__.py:Richard Purdie2006-07-081-1/+1
| | | | | | | | | | | | | | | | | | | 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
* bitbake data module abstraction:Holger Hans Peter Freyther2005-05-171-2/+2
| | | | | | | | | -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
* Adapt bits to the new way of handling the debug level.Chris Larson2004-12-091-1/+1
|
* Initial import.Chris Larson2004-12-071-0/+79