Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [meta-oe][PATCH] ola: add 0.9.1
Date: Wed, 16 Jul 2014 15:28:22 +0200	[thread overview]
Message-ID: <20140716132822.GY2433@jama> (raw)
In-Reply-To: <1405489400-6339-1-git-send-email-koen@dominion.thruhere.net>

[-- Attachment #1: Type: text/plain, Size: 3403 bytes --]

On Wed, Jul 16, 2014 at 07:43:20AM +0200, Koen Kooi wrote:
> Open Lighting Architecture (OLA) is part of the Open Lighting Project
> and provides applications with a mechanism to send and receive DMX512 &
> RDM commands using hardware devices and DMX over IP protocols.
> 
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>  meta-oe/recipes-support/ola/ola_git.bb | 47 ++++++++++++++++++++++++++++++++++
>  1 file changed, 47 insertions(+)
>  create mode 100644 meta-oe/recipes-support/ola/ola_git.bb
> 
> diff --git a/meta-oe/recipes-support/ola/ola_git.bb b/meta-oe/recipes-support/ola/ola_git.bb
> new file mode 100644
> index 0000000..4e24543
> --- /dev/null
> +++ b/meta-oe/recipes-support/ola/ola_git.bb
> @@ -0,0 +1,47 @@
> +SUMMARY = "Open Lighting Architecture - OLA"
> +DESCRIPTION = "The Open Lighting Architecture (OLA) is part of the Open Lighting Project and provides applications with a mechanism to send and receive DMX512 & RDM commands using hardware devices and DMX over IP protocols. This enables software lighting controllers to communicate with hardware either via Ethernet or traditional DMX512 networks. \
> +OLA can also convert DMX512 data sent using DMX over IP protocols from one format to another, allowing devices from different manufacturers to interact with one another. For example a Strand Lighting Console using ShowNet can send DMX512 to an Enttec EtherGate. When combined with a physical DMX interface such as the DMX USB Pro, OLA can send and receive data from wired DMX512 networks."
> +
> +LICENSE = "GPLv2 & LGPLv2.1"
> +LIC_FILES_CHKSUM = "file://LICENCE;md5=f1be0425937acddca9ed750ce30f821d"
> +
> +DEPENDS = "libmicrohttpd avahi libusb1 libftdi cppunit protobuf protobuf-native ola-native"
> +DEPENDS_class-native = "protobuf cppunit"

You need to fix libftdi first:
ERROR: libftdi was skipped: Recipe is blacklisted: BROKEN: needs to be
updated to detect libusb with pkg-config instead of libusb-config

> +PV = "0.9.1"
> +SRCREV = "8c7067514793baaeaa3033d77de163d981d7c73a"
> +SRC_URI = "git://github.com/OpenLightingProject/ola.git;protocol=https"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit autotools pythonnative
> +
> +export BUILD_SYS
> +export HOST_SYS
> +export STAGING_LIBDIR
> +
> +EXTRA_OECONF = " --disable-unittests \
> +               "
> +
> +EXTRA_OECONF_append_class-target = " --with-ola-protoc=${STAGING_BINDIR_NATIVE}/ola_protoc"
> +
> +# -fvisibility-inlines-hidden breaks stuff
> +CXXFLAGS = "${CFLAGS}"
> +
> +# The code is not Werror safe
> +do_configure_prepend() {
> +	sed -i -e 's:-Werror::g' ${S}/configure.ac
> +	sed -i -e 's:-Werror::g' ${S}/Makefile.am
> +}
> +
> +do_install_append_class-native() {
> +    install -d ${D}${bindir}
> +    install -m 0755 ${B}/protoc/ola_protoc ${D}${bindir}
> +}
> +
> +FILES_${PN}-dbg += "${libdir}/*/.debug"
> +FILES_${PN} += "${datadir}/olad ${libdir}/olad/*.so.*"
> +FILES_${PN}-staticdev += "${libdir}/olad/*.a"
> +FILES_${PN}-dev += "${libdir}/olad/*.la ${libdir}/olad/*.so"
> +
> +BBCLASSEXTEND = "native nativesdk"
> -- 
> 1.9.0
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2014-07-16 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  5:43 [meta-oe][PATCH] ola: add 0.9.1 Koen Kooi
2014-07-16 13:28 ` Martin Jansa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140716132822.GY2433@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox