From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] i2c-tools: add support to build python extension
Date: Sun, 5 Apr 2015 23:10:01 +0200 [thread overview]
Message-ID: <20150405211001.GH4134@free.fr> (raw)
In-Reply-To: <1428263326-10320-2-git-send-email-ryanbarnett3@gmail.com>
Ryan, All,
On 2015-04-05 14:48 -0500, Ryan Barnett spake thusly:
> Add a config option to build the python bindings for i2c-tools -
> py-smbus. The steps for building the python bindings is the same as
> the distutil steps that are a part of the python infrastructure.
>
> Signed-off-by: Ryan Barnett <ryanbarnett3@gmail.com>
> CC: Tjeerd Pinkert <t.j.pinkert@vu.nl>
> CC: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
> CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> CC: Baruch Siach <baruch@tkos.co.il>
>
> ---
> Changes v1 -> v2:
> - Fixed spelling in config entry
> - Utilize the python infrastructure variables for environment and
> build/install opts (suggested by Thomas P)
> - Only support python2.7 since this is not compatabile with python3
> (suggested by Baruch)
> ---
> package/i2c-tools/Config.in | 13 +++++++++++++
> package/i2c-tools/i2c-tools.mk | 27 +++++++++++++++++++++++++++
> 2 files changed, 40 insertions(+)
>
> diff --git a/package/i2c-tools/Config.in b/package/i2c-tools/Config.in
> index e83dbd6..6426f30 100644
> --- a/package/i2c-tools/Config.in
> +++ b/package/i2c-tools/Config.in
> @@ -8,3 +8,16 @@ config BR2_PACKAGE_I2C_TOOLS
> EEPROM decoding scripts, and more.
>
> http://www.lm-sensors.org/wiki/I2CTools
> +
> +if BR2_PACKAGE_I2C_TOOLS
> +
> +config BR2_PACKAGE_I2C_TOOLS_PYSMBUS
> + bool "py-smbus"
> + depends on BR2_PACKAGE_PYTHON
> + help
> + Python bindings to smbus from the i2c-tools package.
Well, like Baruch said, I would not add such option, and just build the
Python binding if Python is enabled.
> +comment "i2c-tools py-smbus depends on python2"
> + depends on !BR2_PACKAGE_PYTHON
> +
> +endif
> diff --git a/package/i2c-tools/i2c-tools.mk b/package/i2c-tools/i2c-tools.mk
> index 0115e22..ec2995f 100644
> --- a/package/i2c-tools/i2c-tools.mk
> +++ b/package/i2c-tools/i2c-tools.mk
> @@ -21,4 +21,31 @@ define I2C_TOOLS_INSTALL_TARGET_CMDS
> done
> endef
>
> +# BASE_ENV taken from PKG_PYTHON_DISTUTILS_ENV in package/pkg-python.mk
> +I2C_TOOLS_PYTHON_BASE_ENV = \
> + $(PKG_PYTHON_DISTUTILS_ENV) \
> + CFLAGS="$(TARGET_CFLAGS) -I../include"
Move this define into the conditional, below.
> +# Build/install steps mirror the distutil python package type in the python package
> +# infrastructure
> +ifeq ($(BR2_PACKAGE_I2C_TOOLS_PYSMBUS),y)
Since you'd no longer have an option to enable py-smbus, that
conditional would become:
ifeq ($(BR2_PACKAGE_PYTHON),y)
Also, empty line after the ifeq.
> +I2C_TOOLS_DEPENDENCIES += python
> +
> +define I2C_TOOLS_BUILD_PYSMBUS
> + (cd $(@D)/py-smbus; \
> + $(I2C_TOOLS_PYTHON_BASE_ENV) \
> + $(HOST_DIR)/usr/bin/python setup.py build \
> + $(PKG_PYTHON_DISTUTILS_BUILD_OPTS))
> +endef
> +I2C_TOOLS_POST_BUILD_HOOKS += I2C_TOOLS_BUILD_PYSMBUS
I'd keep the define, ditch the hook, and shoehorn the macro directly
into the build commands, since this is a generic package:
define I2C_TOOLS_BUILD_CMDS
$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D)
$(I2C_TOOLS_BUILD_PYSMBUS)
endef
> +define I2C_TOOLS_INSTALL_PYSMBUS
> + (cd $(@D)/py-smbus; \
> + $(I2C_TOOLS_PYTHON_BASE_ENV) \
> + $(HOST_DIR)/usr/bin/python setup.py install \
> + $(PKG_PYTHON_DISTUTILS_INSTALL_TARGET_OPTS))
> +endef
> +I2C_TOOLS_POST_INSTALL_TARGET_HOOKS += I2C_TOOLS_INSTALL_PYSMBUS
Ditto, include that directly in the install commands.
> +endif
I like it when there is a comment after the endif, refering to the
corresponding ifeq:
endif # BR2_PACKAGE_PYTHON
This helps when the conditional block if more than a few lines long.
Also, empty line before the endif.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-04-05 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-05 19:48 [Buildroot] [PATCH v2 1/2] i2c-tools: add hash file Ryan Barnett
2015-04-05 19:48 ` [Buildroot] [PATCH v2 2/2] i2c-tools: add support to build python extension Ryan Barnett
2015-04-05 21:10 ` Yann E. MORIN [this message]
2015-04-05 21:33 ` Ryan Barnett
2015-04-05 21:47 ` Yann E. MORIN
2015-04-05 21:02 ` [Buildroot] [PATCH v2 1/2] i2c-tools: add hash file Yann E. MORIN
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=20150405211001.GH4134@free.fr \
--to=yann.morin.1998@free.fr \
--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