linux/meta-openembedded.git/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb, branch hardknott

recipes: remove blacklisted recipes

2017-08-31T08:18:33+00:00

* as PNBLACKLIST message says, these recipes are blacklisted for long time and nobody showed any interest to fix them * remove all unused .patch and .inc files as well Signed-off-by: Martin Jansa

recipes: add removal date to PNBLACKLIST messages

2017-04-05T17:36:45+00:00

* 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

farsight: fix implicit pkgconfig dependency causing configure fail

2017-02-22T12:16:54+00:00

In the config log we see: configure:12277: checking whether to build static libraries configure:12281: result: yes configure:12419: checking for x86_64-overc-linux-pkg-config configure:12452: result: no configure:12462: checking for pkg-config configure:12495: result: no configure:12801: Using Farsight2 source release as package name configure:12825: Using Unknown package origin as package origin configure:12879: Using /usr/libexec/gst-install-plugins-helper as plugin install helper configure:12953: checking for NICE configure:13022: error: Need libnice >= 0.0.9 While it libnice that fails configure, it is the absence of pkg-config several lines above that causes the failure, as libnice is in the sysroot. For most build hosts, you'll have to remove the default binary that lives in /usr/bin/pkg-config in order to see this failure. Cc: Martin Jansa Signed-off-by: Paul Gortmaker Signed-off-by: Martin Jansa

recipes: blacklist recipes depending on blacklisted recipes

2017-02-13T17:44:35+00:00

Signed-off-by: Martin Jansa

libnice, farsight2: unblacklist as libnice's nice.pc issue fixed.

2016-05-10T18:18:56+00:00

* Update do_compile_append where it was updating *.pc from ${S} and removing staging dir folder. Now we have seperate build folder where packages get build. We have to search pc in ${B} not in ${S}. After updating the tmp dir path is removed from nice.pc file. * Remove PNBLACKLIST for libnice and farsight2 recipes. Signed-off-by: Noor Ahsan Signed-off-by: Martin Jansa

libnice, farsight2, pidgin: Blacklist because libnice's nice.pc

2016-02-25T16:47:28+00:00

Signed-off-by: Martin Jansa

meta-oe: use BPN in SRC_URI

2014-07-15T12:56:55+00:00

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 Signed-off-by: Martin Jansa

farsight2: add PACKAGECONFIG for gupnp

2013-07-30T09:17:12+00:00

* it's autodetected from sysroot * add PACKAGECONFIG to make it deterministic Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* 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 Acked-by: Koen Kooi

recipes: bump PR to rebuild after libffi5 -> libffi6

2012-09-20T08:02:45+00:00

Signed-off-by: Martin Jansa Signed-off-by: Koen Kooi