summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-extended/subsurface
Commit message (Collapse)AuthorAgeFilesLines
* recipes: add removal date to PNBLACKLIST messagesMartin Jansa2017-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | * based on discussion in pndeprecated thread: https://patchwork.openembedded.org/patch/137573/ update the messages to warn possible users that the recipe will be removed before the end of the next development cycle (before Yocto 2.4 is released). * updated with: sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs` * then noticed couple recipes being blacklisted only based on DISTRO_FEATURES, so removed those: meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb meta-oe/recipes-navigation/gypsy/gypsy.inc meta-oe/recipes-navigation/navit/navit.inc meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb * if it isn't fixed by this date, it's fair game to be removed whenever someone gets around to i Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* PNBLACKLIST: use weak assignmentsMartin Jansa2014-12-171-1/+1
| | | | | | | * this makes it easier to unblacklist it from local.conf which is parsed before the recipes Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* subsurface: blacklist until it's upgraded for libdivecomputer compatibilityMartin Jansa2014-10-103-57/+7
| | | | | | | * I've started with upgrade, but requires lot more changes which I'm not comfortable to finish on something I cannot test in runtime Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* subsurface: Adjust dependencies to match eglibc -> glibc moveKhem Raj2014-09-261-1/+1
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* subsurface: Fix libxml and libm build failuresRichard Purdie2014-07-223-1/+42
| | | | | | | Use pkg-config to find libxml2 and also link against libm to avoid build failures. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET2014-02-231-1/+1
| | | | | | | | | | | | | 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>
* subsurface: add dependency on gconfMartin Jansa2013-08-141-1/+1
| | | | | | | | | | | | * fails without | Package gconf-2.0 was not found in the pkg-config search path. | Perhaps you should add the directory containing `gconf-2.0.pc' | to the PKG_CONFIG_PATH environment variable | No package 'gconf-2.0' found | main.c:7:32: fatal error: gconf/gconf-client.h: No such file or directory | #include <gconf/gconf-client.h> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* recipes: Unify indentationMartin Jansa2013-04-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* subsurface: update to 1.1 release, start using gitpkgvKoen Kooi2011-10-241-4/+6
| | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* subsurface: inital addKoen Kooi2011-10-151-0/+28
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>