[bitbake-devel] [OE-core] BitBake changes in the Yocto Project 1.5 cycle

[Marcin Juszkiewicz]

W dniu 22.04.2013 16:16, Richard Purdie pisze:
> I've been giving some thought to where BitBake needs to go in the 
> future in order to deliver for its users. It started life as a 
> commandline utility and its grown a lot since it was first created.
> I think there are some key decisions that need to be taken to ensure 
> its future growth.

There is one thing which kind of bothers me. "ERROR" message which is
just a warning. Like:

ERROR: libelf is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libasm is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libdw is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libdw-dev is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libasm-dev is listed in PACKAGES multiple times, this leads to packaging errors.
ERROR: libelf-dev is listed in PACKAGES multiple times, this leads to packaging errors.

If it is error then let BitBake exit instead of doing task. If it is
not error but just a warning then let it be renamed?

My recent build failed with:

--------
NOTE: recipe linaro-image-minimal-1.0-r0: task do_rm_work_all: Started
NOTE: recipe linaro-image-minimal-1.0-r0: task do_rm_work_all: Succeeded
NOTE: Tasks Summary: Attempted 2247 tasks of which 915 didn't need to be rerun and all succeeded.

Summary: There were 3 WARNING messages shown.
Summary: There were 6 ERROR messages shown, returning a non-zero exit code.
Build step 'Execute shell' marked build as failure
--------

"all succeeded" does not look like a reason to fail a build.