meta-openembedded/meta-multimedia
Tim Orling 6898dae64e vlc: use AM_PATH_LIBGCRYPT instead of libgcrypt-config
* AM_PATH_LIBGCRYPT exists for a reason, why not use it?

Signed-off-by: Tim Orling <TicoTimo@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-07-22 00:01:58 +02:00
..
conf meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
recipes-connectivity/gupnp gssdp: Upgrade to 0.14.8, drop previous versions 2014-07-22 00:01:51 +02:00
recipes-dvb recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues 2014-02-23 23:20:02 +01:00
recipes-mediacentre/xbmc emacs, mplayer2, gnome-mplayer, xbmc, libimobiledevice, ifuse, tk: blacklist recipes failing in world builds 2014-05-09 14:59:01 +02:00
recipes-mkv mkvtoolnix: fix build with B!=S 2014-06-21 13:06:14 +02:00
recipes-multimedia vlc: use AM_PATH_LIBGCRYPT instead of libgcrypt-config 2014-07-22 00:01:58 +02:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README README: show github mirror URL in layer dependencies 2013-05-03 13:32:03 +02:00

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD

URI: git://github.com/openembedded/meta-oe.git
layers: meta-oe, meta-ruby
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][PATCH

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainers: Koen Kooi <koen@dominion.thruhere.net>
                        Martin Jansa <martin.jansa@gmail.com>