Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python-can: new package
Date: Sun, 31 May 2015 18:17:06 +0200	[thread overview]
Message-ID: <556B3402.1000309@mind.be> (raw)
In-Reply-To: <1432890762-24842-1-git-send-email-angelo.compagnucci@gmail.com>

On 05/29/15 11:12, Angelo Compagnucci wrote:
> This patch provides controller area network support for Python.
> 
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> ---
>  package/Config.in                |  1 +
>  package/python-can/Config.in     |  6 ++++++
>  package/python-can/python-can.mk | 15 +++++++++++++++
>  3 files changed, 22 insertions(+)
>  create mode 100644 package/python-can/Config.in
>  create mode 100644 package/python-can/python-can.mk
> 
> diff --git a/package/Config.in b/package/Config.in
> index d18343c..6661240 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -577,6 +577,7 @@ if BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
>  menu "external python modules"
>  	source "package/python-alsaaudio/Config.in"
>  	source "package/python-bottle/Config.in"
> +	source "package/python-can/Config.in"
>  	source "package/python-certifi/Config.in"
>  	source "package/python-cffi/Config.in"
>  	source "package/python-cheetah/Config.in"
> diff --git a/package/python-can/Config.in b/package/python-can/Config.in
> new file mode 100644
> index 0000000..6b4e0fa
> --- /dev/null
> +++ b/package/python-can/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_PYTHON_CAN
> +	bool "python-can"
> +	help
> +	  This module provides controller area network support for Python.
> +
> +	  https://bitbucket.org/hardbyte/python-can
> diff --git a/package/python-can/python-can.mk b/package/python-can/python-can.mk
> new file mode 100644
> index 0000000..50477a3
> --- /dev/null
> +++ b/package/python-can/python-can.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# python-can
> +#
> +################################################################################
> +
> +PYTHON_CAN_VERSION = ae5b6cf
> +PYTHON_CAN_SITE = https://bitbucket.org/hardbyte/python-can
> +PYTHON_CAN_SITE_METHOD = hg

 I generally prefer to use the normal http download method:

PYTHON_CAN_SITE = https://bitbucket.org/hardbyte/python-can/get/
PYTHON_CAN_SOURCE = $(PYTHON_CAN_VERSION).tar.bz2


 Regards,
 Arnout

> +PYTHON_CAN_LICENSE = GPLv3
> +PYTHON_CAN_LICENSE_FILES = LICENSE.txt
> +PYTHON_CAN_DEPENDENCIES = python
> +PYTHON_CAN_SETUP_TYPE = setuptools
> +
> +$(eval $(python-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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      parent reply	other threads:[~2015-05-31 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  9:12 [Buildroot] [PATCH] package/python-can: new package Angelo Compagnucci
2015-05-30  7:27 ` Thomas Petazzoni
2015-05-31 16:17 ` Arnout Vandecappelle [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=556B3402.1000309@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