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] python-ipy: new package
Date: Tue, 01 Oct 2013 18:40:56 +0200	[thread overview]
Message-ID: <524AFB18.1000203@mind.be> (raw)
In-Reply-To: <1380318149-22696-1-git-send-email-mlweber1@rockwellcollins.com>

On 09/27/13 23:42, Matt Weber wrote:
>
> Signed-off-by: Matt Weber <mlweber1@rockwellcollins.com>
> ---
>   package/Config.in                |    1 +
>   package/python-ipy/Config.in     |    8 ++++++++
>   package/python-ipy/python-ipy.mk |   30 ++++++++++++++++++++++++++++++
>   3 files changed, 39 insertions(+), 0 deletions(-)
>   create mode 100644 package/python-ipy/Config.in
>   create mode 100644 package/python-ipy/python-ipy.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index c6ea66b..2d05560 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -389,6 +389,7 @@ source "package/python-bottle/Config.in"
>   source "package/python-crc16/Config.in"
>   source "package/python-dpkt/Config.in"
>   source "package/python-id3/Config.in"
> +source "package/python-ipy/Config.in"
>   source "package/python-mad/Config.in"
>   source "package/python-meld3/Config.in"
>   source "package/python-netifaces/Config.in"
> diff --git a/package/python-ipy/Config.in b/package/python-ipy/Config.in
> new file mode 100644
> index 0000000..bead932
> --- /dev/null
> +++ b/package/python-ipy/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_PYTHON_IPY
> +	bool "python-ipy"
> +	depends on BR2_PACKAGE_PYTHON
> +	help
> +	  IPy - class and tools for handling of IPv4 and
> +	  IPv6 addresses and networks.
> +
> +	  https://github.com/haypo/python-ipy/
> diff --git a/package/python-ipy/python-ipy.mk b/package/python-ipy/python-ipy.mk
> new file mode 100644
> index 0000000..9e09762
> --- /dev/null
> +++ b/package/python-ipy/python-ipy.mk
> @@ -0,0 +1,30 @@
> +################################################################################
> +#
> +# python-ipy
> +#
> +################################################################################
> +
> +PYTHON_IPY_VERSION = 0.75-0-g58006fb
> +PYTHON_IPY_SOURCE  = haypo-python-ipy-IPy-$(PYTHON_IPY_VERSION).tar.gz
> +PYTHON_IPY_SITE    = https://github.com/haypo/python-ipy/tarball/IPy-0.75
> +PYTHON_IPY_DEPENDENCIES = host-python python
> +PYTHON_IPY_LICENSE = BSD-3c
> +PYTHON_IPY_LICENSE_FILES = COPYING
> +
> +define PYTHON_IPY_BUILD_CMDS
> +	(cd $(@D); \
> +		CC="$(TARGET_CC)" \
> +		CFLAGS="$(TARGET_CFLAGS) -I$(STAGING_DIR)/usr/include" \
> +		LDSHARED="$(TARGET_CC) -shared" \
> +		LDFLAGS="$(TARGET_LDFLAGS) -L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib" \

  The -I and -L shouldn't be needed - if they are, something else must be 
wrong...

  I realize the other python packages don't do it, but why not use 
TARGET_CONFIGURE_OPTS?

  Regards,
  Arnout

> +		$(HOST_DIR)/usr/bin/python setup.py build_ext \
> +		--include-dirs=$(STAGING_DIR)/usr/include/python$(PYTHON_VERSION_MAJOR) \
> +	)
> +	(cd $(@D); $(HOST_DIR)/usr/bin/python setup.py build)
> +endef
> +
> +define PYTHON_IPY_INSTALL_TARGET_CMDS
> +	(cd $(@D); $(HOST_DIR)/usr/bin/python setup.py install --prefix=$(TARGET_DIR)/usr)
> +endef
> +
> +$(eval $(generic-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

  reply	other threads:[~2013-10-01 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 21:42 [Buildroot] [PATCH 1/1] python-ipy: new package Matt Weber
2013-10-01 16:40 ` Arnout Vandecappelle [this message]
2013-10-01 19:51   ` Matthew Weber

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=524AFB18.1000203@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