DLNA Media Server Virtual Appliance: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 25: Line 25:
* build the image using the guacamayo-image-mediaserver target
* build the image using the guacamayo-image-mediaserver target
  bitbake <tt>guacamayo-image-mediaserver</tt> [TODO]  
  bitbake <tt>guacamayo-image-mediaserver</tt> [TODO]  
For testing purposes, demo content can be added by inserting the following line to <tt>build/conf/local.conf</tt>:
For testing purposes, demo content can be added by inserting the following line into <tt>build/conf/local.conf</tt>:


  [...]
  [...]
  IMAGE_FEATURES_append = " guacamayo-demos"
  IMAGE_FEATURES_append = " guacamayo-demos"
  [...]
  [...]

Revision as of 16:46, 5 September 2012

Introduction

A DLNA[1] Media Server is a device that stores media content that can be accessed by media players and rederers found in the same local network. The goal was creating a minimal solution to meet theese requirements. This was achieved using the tools provided by the yocto project through the creation of the meta-dlna layer.

Package dependencies

The solution was build around rygel[2], an application used for media content sharing on a home network. Rygel implements its functionality through a plugin mechanism. A solution provided by Tracker. An alternative solution is uses the MediaExport plugin which exports files and folders over the network. This was preffered because it represents a more lightweight solution.

How to integrate DLNA to a poky distribution

The meta-dlna layer was created using the combo-layer tool[3]. To use it follow the next steps:

  • Copy the meta-dlna folder into the root directory of a poky distribution. Cd into the poky folder.
  • Add the layer to build/conf/bblayers.conf:
[...]
BBLAYERS="
         $POKY_HOME/meta-dlna/meta-guacamayo
[...]
  • Add some extra features to build/local.conf:
[...]
DISTRO_FEATURES = "ext2 largefile usbhost xattr nfs zeroconf pci ${DISTRO_FEATURES_LIBC} x11" 
[...]
  • source the oe-init-env script
  • build the image using the guacamayo-image-mediaserver target
bitbake guacamayo-image-mediaserver [TODO] 

For testing purposes, demo content can be added by inserting the following line into build/conf/local.conf:

[...]
IMAGE_FEATURES_append = " guacamayo-demos"
[...]