Age | Commit message (Collapse) | Author |
|
* Migrate libass.inc into recipe - nothing else uses it
* Use git repo to avoid github checksum trouble
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
|
|
License checksum was changed by some back and forth [1-2] - now it is really
ISC again.
[1] https://github.com/libass/libass/commit/9422a80578bc44f662f07edf723f85239a0579f5
[2] https://github.com/libass/libass/commit/cde05e0716ef2b74530633d463ad7f6d0b94ac61
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
|
|
* mpv requires newer libass to build
* move SRC_URI from Google Code to GitHub
* ENCA support has been removed https://github.com/libass/libass/pull/197
remove --enable-enca which is now an [unknown-configure-option]
* Fix [textrel] for x86 targets
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Fixed SRC_URI:
* ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV}
* ${P} -> ${BP}
Otherwise we would meet do_fetch errors when we do the multilib, native
or nativesdk build.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Change-Id: Ib748bfbd3437e3cfdeaba7283b99aa55ad479a6a
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* it's autodetected from sysroot
* add PACKAGECONFIG to make it deterministic
* runtime dependencies for glib-2.0 harfbuzz libffi libicudata libicule libicuuc libstdc++ are added
only when harfbuzz is detected
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>
|
|
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* old version wasn't compatible with libpng-1.5 from oe-core
* COPYING was updated with ISC text old 0.9.11 was GPLv2
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|