Age | Commit message (Collapse) | Author |
|
|
|
For our french and strange friends place LC_ALL=C in all task calls.
This should give us english log messages.
|
|
- 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
|
|
- those scripts are not called by hand by bitbake users
and most of package linting tools (lintian/Debian, rpmlint/Fedora)
complain about not executable scripts.
- if someone want to run them by hand then he will be able to do it
with calling 'python SCRIPT'
|
|
|
|
|
|
* Add version of stamp_is_current that works with cached data
* Tweak mkstamp to work over broken? NFS filesystems (simply opening
the file for write access wasn't enough to change the file's timestamp)
* Have add_task create _task_deps variable containing various task flags
for cache use
|
|
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
|
|
In the case of rm_work.bbclass we might have deleted the
directory where we come from. Do not fail to avoid
the issues described in #1017
|
|
- Remove some stale inactive code
|
|
Create a work in progress version for
better_execute. With advanced error reporting
facilities.
bitbake/lib/bb/build.py:
Use better_execute
bitbake/parse/parse_py/BBHandler.py:
Use better_execute instead of exex
|
|
We compile strings into code. In case of erros the traceback
is not useful at all. It doesn't print the function name,
accurate line number etc.
Introduce a better_compile method that excepts the Error
and prints the surrounding lines of code.
We make use of it on the parsing level and execution level
of python methods.
|
|
The function should be shielded against the posibility that prevdir could be removed by the function.
|
|
-Fix the task_cache as reference assumption as described
in bug report #60
Patch courtsey keturn
|
|
- remove event property
- submit descriptive error messages when raising event exceptions
|
|
Do not assume we hold a reference to the variable
we got with a bb.data.getVar*. Always set changes
back to the variable.
|
|
-Move a createCopy method into data.py
-Make code creating deepcopies of the data instance
use this new createCopy
|
|
to be more consistent with the other events.
|
|
mangling OVERRIDES in bb.data.exec_task().
|
|
|
|
|
|
|