aboutsummaryrefslogtreecommitdiffstats
path: root/meta-multimedia/recipes-multimedia/dleyna
AgeCommit message (Collapse)Author
2016-03-14media-service-demo: remove the recipeAlexander Kanavin
It hasn't been updated in years, and depends on pygtk, which is obsolete and incompatible with pygobject 3.x (and so is no longer provided). Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2015-12-18dleyna-renderer: Add recipeManuel Bachmann
dleyna-renderer is a library for implementing Digital Media (DLNA) Renderers, and also provides a sample implementation of such a renderer. "dleyna-renderer-service" is designed to be started and consumed using D-Bus. Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-12-18dleyna-server: Add recipeManuel Bachmann
dleyna-server is a library for implementing Digital Media (DLNA) Servers, and also provides a sample implementation of such a server. "dleyna-server-service" is designed to be started and consumed using D-Bus. Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-12-18dleyna-connector-dbus: Add recipeManuel Bachmann
dleyna-connector-dbus is a D-Bus connector library depending on "dleyna-core", and needed by dLeyna implementations (most notably "dleyna-server" and "dleyna-renderer"). It allows them to discover D-Bus buses, and to be started via D-Bus services files. Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-12-18dleyna-core: Add recipeManuel Bachmann
dleyna-core is a library of utility functions needed by other dLeyna packages (most notably "dleyna-connector-dbus" "dleyna-server" and "dleyna-renderer"). It provides APIs for logging, error, settings, task management and an IPC abstraction API. Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-10-23media-service-upnp: Update to 0.5.0Manuel Bachmann
Update to latest version (requires gupnp-dlna 0.9.4). Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-12-17PNBLACKLIST: use weak assignmentsMartin Jansa
* 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>
2014-06-21renderer-service-upnp: Blacklist because of broken with B!=SMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-06-21recipes: add missing pkgconfig class inheritsRichard Purdie
* These recipes all use pkg-config in some way but were missing dependencies on the tool, this patch adds them. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-09-17dleyna: switch to git clones instead of generated tarballsRoss Burton
The tarballs used were the dynamically-generated tarballs from github, which recently have changed checksum. Avoid this problem entirely by fetching from git, locked to the relevant tag. Signed-off-by: Ross Burton <ross.burton@intel.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-09-03remove the unnecessary protocol parametersJackie Huang
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>
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>
2013-01-09media-service-demo: add snapshot from gitRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-01-09renderer-service-upnp: add 0.3.0Ross Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-01-09media-service-upnp: add 0.4.0Ross Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>