Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-protobuf: Add support for Python implementation of Google's Protocol Buffers
Date: Fri, 07 Sep 2012 08:23:57 +0200	[thread overview]
Message-ID: <504992FD.4080702@visionsystems.de> (raw)
In-Reply-To: <20120906205831.GA12993@localhost.comm5.com.br>

Am 06.09.2012 22:58, schrieb Thiago A. Correa:
> python-protobuf: Add support for Python implementation of Google's Protocol Buffers
> 
> Signed-off-by: Thiago A. Correa <thiago.correa@gmail.com>
> ---
>  package/python-protobuf/Config.in          |   11 +++++++++++
>  package/python-protobuf/python-protobuf.mk |   28 ++++++++++++++++++++++++++++
>  2 files changed, 39 insertions(+), 0 deletions(-)
>  create mode 100644 package/python-protobuf/Config.in
>  create mode 100644 package/python-protobuf/python-protobuf.mk
> 
> diff --git a/package/python-protobuf/Config.in b/package/python-protobuf/Config.in
> new file mode 100644
> index 0000000..d2bf70d
> --- /dev/null
> +++ b/package/python-protobuf/Config.in
> @@ -0,0 +1,11 @@
> +config BR2_PACKAGE_PYTHON_PROTOBUF
> +	bool "python-protobuf"
> +	depends on BR2_PACKAGE_PYTHON
> +	select BR2_PACKAGE_PYTHON_SETUPTOOLS
> +	help
> +	  Python implementation of the Google Protocol Buffers.
> +
> +	  Protocol buffers are Google's language-neutral, platform-neutral,
> +	  extensible mechanism for serializing structured data.
> +
> +	  http://code.google.com/p/protobuf/
> diff --git a/package/python-protobuf/python-protobuf.mk b/package/python-protobuf/python-protobuf.mk
> new file mode 100644
> index 0000000..d632e00
> --- /dev/null
> +++ b/package/python-protobuf/python-protobuf.mk
> @@ -0,0 +1,28 @@
> +#############################################################
> +#
> +# python-protobuf
> +#
> +#############################################################
> +
> +PYTHON_PROTOBUF_VERSION = $(PROTOBUF_VERSION)
> +PYTHON_PROTOBUF_SOURCE  = $(PROTOBUF_SOURCE)
> +PYTHON_PROTOBUF_SITE    = $(PROTOBUF_SITE)
> +PYTHON_PROTOBUF_LICENSE = BSD-3c
> +PYTHON_PROTOBUF_LICENSE_FILES = COPYING.txt
> +
> +PYTHON_PROTOBUF_DEPENDENCIES = python host-python-setuptools host-python-distutilscross host-protobuf
> +
> +define PYTHON_PROTOBUF_BUILD_CMDS
> +	(cd $(@D)/python; \
> +		PYTHONXCPREFIX="$(STAGING_DIR)/usr/" \
> +		LDFLAGS="-L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib" \
> +		PATH=$(HOST_PATH) \
> +	$(HOST_DIR)/usr/bin/python setup.py build -x)
> +endef
> +
> +define PYTHON_PROTOBUF_INSTALL_TARGET_CMDS
> +	(cd $(@D)/python; PYTHONPATH=$(TARGET_DIR)/usr/lib/python$(PYTHON_VERSION_MAJOR)/site-packages \
> +	$(HOST_DIR)/usr/bin/python setup.py install --prefix=$(TARGET_DIR)/usr)
> +endef
> +
> +$(eval $(generic-package))
> 

I'm missing package/Config.in, where python-protobuf can be activated.

Best regards,
Yegor

  reply	other threads:[~2012-09-07  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 20:58 [Buildroot] [PATCH] python-protobuf: Add support for Python implementation of Google's Protocol Buffers Thiago A. Correa
2012-09-07  6:23 ` Yegor Yefremov [this message]
2012-09-08 13:22   ` Thiago A. Corrêa
  -- strict thread matches above, loose matches on Subject: below --
2012-09-08 13:41 Thiago A. Correa

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=504992FD.4080702@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --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