Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libmraa: new package
Date: Tue, 5 Jan 2016 01:48:46 +0100	[thread overview]
Message-ID: <568B12EE.30106@mind.be> (raw)
In-Reply-To: <1451936760-1654-1-git-send-email-pieterjan.camerlynck@gmail.com>

 Hi Pieterjan,

On 04-01-16 20:46, Pieterjan Camerlynck wrote:
> libmraa provides a unified interface for IO on Galileo, Edison,
> Raspberry Pi and others
> 
> Signed-off-by: Pieterjan Camerlynck <pieterjan.camerlynck@gmail.com>
> ---
>  package/Config.in          |  1 +
>  package/libmraa/Config.in  | 17 +++++++++++++++++
>  package/libmraa/libmraa.mk | 22 ++++++++++++++++++++++
>  3 files changed, 40 insertions(+)
>  create mode 100644 package/libmraa/Config.in
>  create mode 100644 package/libmraa/libmraa.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index 442021f..52f6b5b 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -930,6 +930,7 @@ menu "Hardware handling"
>  	source "package/libiqrf/Config.in"
>  	source "package/libllcp/Config.in"
>  	source "package/libmbim/Config.in"
> +	source "package/libmraa/Config.in"
>  	source "package/libnfc/Config.in"
>  	source "package/libpciaccess/Config.in"
>  	source "package/libphidget/Config.in"
> diff --git a/package/libmraa/Config.in b/package/libmraa/Config.in
> new file mode 100644
> index 0000000..cfbe37c
> --- /dev/null
> +++ b/package/libmraa/Config.in
> @@ -0,0 +1,17 @@
> +config BR2_PACKAGE_LIBMRAA
> +	bool "libmraa"
> +	depends on BR2_INSTALL_LIBSTDCPP

 Actually it doesn't contain any C++ code as far as I can see. So you should
patch CMakeLists.txt to set

project (mraa C)

(and send that patch upstream).

> +	depends on BR2_TOOLCHAIN_HAS_THREADS
> +	depends on !BR2_STATIC_LIBS

 I don't see anything that would require dynamic libraries. Can you add a
comment why this is needed?

> +	depends on BR2_ARM_CPU_ARMV7A || BR2_i386 || BR2_x86_64

 It actually builds on any platform, except that the CMakeLists.txt explicitly
checks for arm or x86. But there is nothing armv7-specific, and supposedly the
library would still be useful on generic boards. So I'd just put BR2_arm.

> +	help
> +	  Libmraa is a C/C++ library with bindings to javascript & python

 Well, the js and python bindings aren't built... But that could be added in
follow-up patches so OK.

> +	  to interface with the IO on Galileo, Edison & other platforms,
> +	  with a structured and sane API where port names/numbering matches
> +	  the board that you are on.
> +
> +	  http://iotdk.intel.com/docs/master/mraa
> +
> +comment "libmraa needs a toolchain w/ C++, threads, dynamic library"
> +	depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP \
> +		|| BR2_STATIC_LIBS
> diff --git a/package/libmraa/libmraa.mk b/package/libmraa/libmraa.mk
> new file mode 100644
> index 0000000..099e883
> --- /dev/null
> +++ b/package/libmraa/libmraa.mk
> @@ -0,0 +1,22 @@
> +################################################################################
> +#
> +# libmraa
> +#
> +################################################################################
> +
> +LIBMRAA_VERSION = v0.9.0
> +LIBMRAA_SITE = $(call github,intel-iot-devkit,mraa,$(LIBMRAA_VERSION))

 Upstream calls it mraa, not libmraa, so we prefer to stick to the same name.

 Otherwise looks good.

 Regards,
 Arnout

> +LIBMRAA_LICENSE = MIT
> +LIBMRAA_LICENSE_FILES = COPYING
> +LIBMRAA_INSTALL_STAGING = YES
> +
> +LIBMRAA_CONF_OPTS += \
> +	-DBUILDSWIG=OFF \
> +	-DUSBPLAT=OFF \
> +	-DFTDI4222=OFF \
> +	-DIPK=OFF \
> +	-DRPM=OFF \
> +	-DENABLEEXAMPLES=OFF \
> +	-DTESTS=OFF
> +
> +$(eval $(cmake-package))
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-01-05  0:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 19:46 [Buildroot] [PATCH 1/1] libmraa: new package Pieterjan Camerlynck
2016-01-05  0:48 ` Arnout Vandecappelle [this message]
2016-01-05 17:50   ` Pieterjan Camerlynck
2016-01-05 20:11 ` [Buildroot] [PATCH v2] mraa: " Pieterjan Camerlynck
2016-01-06 12:56   ` Samuel Martin
2016-01-06 17:24   ` [Buildroot] [PATCH v3] " Pieterjan Camerlynck
2016-01-06 21:44     ` Samuel Martin
2016-01-09  0:10     ` Arnout Vandecappelle
2016-01-09  8:36     ` [Buildroot] [PATCH v4 1/1] " Pieterjan Camerlynck
2016-01-12 20:59       ` Peter Korsgaard

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=568B12EE.30106@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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