aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/fltk
AgeCommit message (Collapse)Author
2015-12-18fltk: upgrade from version 1.1.10 to 1.3.3Yi Zhao
- backport patch from trunk to fix build failure with jpeg-9 library - add PACKAGECONFIG for opengl, xinerama, xfixes, xcursor to fix [build-deps] qa warnings - rebase patches against the new version and drop the useless patches - cleanup the host buildpaths from fltk-config Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-05-13fltk: fix PN -> BPN for multilibYi Zhao
Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-03-06fltk: Replace use of freetype-config with pkg-config Drop blacklist entryFlorian Boor
Tested building for MIPS 32bit QEMU Signed-off-by: Florian Boor <florian@kernelconcepts.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-02-27fltk: blacklist, still uses /usr/bin/freetype-configMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-07-22fltk: Disable separate build since its brokenRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-02-23recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET
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>
2013-04-15recipes: Unify indentationMartin Jansa
* 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>
2012-12-23fltk: fix build with libpng-1.5 from oe-coreMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2012-10-28Replace bb.data.* with d.*Paul Eggleton
Used sed expression given here: http://lists.linuxtogo.org/pipermail/openembedded-core/2011-November/012373.html Plus an additional expression for .expand. Full expression is: sed \ -e 's:bb.data.\(setVar([^,]*,[^,]*\), \([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,]*,[^,]*,[^,]*\), \([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,]*\), \([^, ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,]*,[^,]*\), \([^, ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,]*,[^,]*\), \([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,]*\), \([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(expand([^,]*\), \([^ )]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` Some minor correction in systemd.bbclass was needed for some expressions that didn't quite match the regex in the desired way; additionally a few instances were manually changed. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2012-07-31fbreader, fltk, gpm, iksemel, joe, links, ode, openldap, opensync, xchat: ↵Martin Jansa
import from meta-smartphone Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>