base_contains() is a compatibility wrapper and may warn in the future, so
replace all instances with bb.utils.contains().
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fails without it:
| checking mad.h usability... no
| checking mad.h presence... no
| checking for mad.h... no
| configure: error: Could not find a required library. Please see the README for your platform.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* otherwise AUTOINC in SRCPV isn't expanded and stays in PKGR and
filename
* I haven't seen it documented anywhere, but oe-core is full of checks
like this:
meta/classes/migrate_localcount.bbclass: if not 'AUTOINC' in pv:
meta/classes/package.bbclass: if 'AUTOINC' in pkgv:
meta/classes/prexport.bbclass: if 'AUTOINC' in ver:
meta/classes/prserv.bbclass: if 'AUTOINC' in pv:
so it looks intentional
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The custom XBMC XB_FIND_SONAME macro doesn't work with the gold linker, backport a patch to fix it
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
This allow the package to build fine. On the test board it didn't show
anything in display but it seems to be hardware specific issue.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Ross Burton
Martin Jansa
Tim Orling
Matthieu CRAPET
Jackie Huang
Koen Kooi
Otavio Salvador
Paul Eggleton