aboutsummaryrefslogtreecommitdiffstats
path: root/classes
Commit message (Collapse)AuthorAgeFilesLines
* 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