Age | Commit message (Collapse) | Author |
|
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.
|