| Age | Commit message (Collapse) | Author |
|---|
|
Various misc changes to convert bitbake to python3 which don't warrant
separation into separate commits.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This sets the scene for removing the default False for expansion from
getVarFlag. This would later allow True to become the expand default.
On the most part this is an automatic translation with:
sed -e 's:\(\.getVarFlag([^,()]*, [^,()]*\)):\1, False):g' -i `grep -ril getVar *`
There should be no functional change from this patch.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From Poky rev: affd0907253387cee0ba0c7e9f92bcc109895446)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
At the moment it bugs me a lot that we only have one effective logging
level for bitbake, despite the logging module having provision to do
more advanced things. This patch:
* Changes the core log level to the lowest level we have messages of
(DEBUG-2) so messages always flow through the core logger
* Allows build.py's task logging code to log all the output regardless
of what output is on the console and sets this so log files now
always contain debug level messages even if these don't appear
on the console
* Moves the verbose/debug/debug-domains code to be a UI side setting
* Adds a filter to the UI to only print the user requested output.
The result is more complete logfiles on disk but the usual output to the
console.
There are some behaviour changes intentionally made by this patch:
a) the -v option now controls whether output is tee'd to the console.
Ultimately, we likely want to output a message to the user about where the
log file is and avoid placing output directly onto the console for every
executing task.
b) The functions get_debug_levels, the debug_levels variable, the
set_debug_levels, the set_verbosity and set_debug_domains functions are
removed from bb.msg.
c) The "logging" init function changes format.
d) All messages get fired to all handlers all the time leading to an
increase in inter-process traffic. This could likely be hacked around
short term with a function for a UI to only request events greater than
level X. Longer term, having masks for event handlers would be better.
e) logger.getEffectiveLevel() is no longer a reliable guide to what
will/won't get logged so for now we look at the default log levels instead.
[YOCTO #304]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* This patch fixes a cosmetic issue currently we get with master
WARNING: /home/kraj/work/bitbake/lib/bb/fetch2/__init__.py:733:
DeprecationWarning: Call to deprecated function bb.mkdirhier: Please use bb.utils.mkdirhier instead. bb.mkdirhier("%s/%s" % (rootdir, destdir))
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
BitBake trunk is now GPLv2 only, no mix of
MIT,FreeBSD License is left.
Update GPL headers to point to the correct
address of the FSF
Update the list of authors. Uli Luckas,
Seb Frankengul and Tim Amsell contributed to
the sourcecode as well
|
|
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
|
|
Make it work with python2.3 and python2.4
|
|
-Use paragraphs instead of 'pre'. This enables line
wrapping for too big comments
|
|
-Do not link to keys.html and groups.html, use the right
site
-Make it possible to have descriptions for groups as well
|
|
-Work on case insensitive filesystems where keys.html == keyS.html
-Create all_groups.html and all_keys site
-Sort the keys in a group
-Emit the ',' only when needed
|
|
-We do not need make, we only need bb.parse
|
|
-Sort the groups (I had not expected to still see this on my disk)
|
|
-Fix whitespaces
-Sort the keynames in the key overview
-Sort the related groups and keys alphabetical as well
-Fix the URL from the Group description to the contained
keys s/group/key/
|
|
-Small utility to generate a Hyper Linked online version
out of documentation.conf.
An example can be found here:http://handhelds.org/~zecke/oe_html/
TODO:
-Beautify the HTML output (shameless rip off from gtkdoc)
-Sort the keys
-Fix and extend OpenEmbedded's documentation.conf to follow the
simple ruleset
KEY[doc] = "This is the description. It can go on \
@see MOO_RELATED, FOO_DOO, GRUFT, BLUR, TOCOTRONIC @group rock, POP \
NewWave"
It will extract the description, related keys (everything after @see
separated by ',') and the groups this key is in. This simple rules
should and could bring us forward.
|
Richard Purdie
Khem Raj
Chris Larson
Richard Purdie
Holger Hans Peter Freyther