All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] python-cffi: add host variant
Date: Thu, 24 Dec 2015 22:46:45 +0100	[thread overview]
Message-ID: <20151224214645.GA3738@free.fr> (raw)
In-Reply-To: <1450992641-8618-3-git-send-email-yegorslists@googlemail.com>

Yegor, All,

On 2015-12-24 22:30 +0100, Yegor Yefremov spake thusly:
> Host variant is needed to build python-cryptography package.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  package/python-cffi/python-cffi.mk | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/package/python-cffi/python-cffi.mk b/package/python-cffi/python-cffi.mk
> index 70fbe02..a6e4107 100644
> --- a/package/python-cffi/python-cffi.mk
> +++ b/package/python-cffi/python-cffi.mk
> @@ -11,5 +11,7 @@ PYTHON_CFFI_SETUP_TYPE = setuptools
>  PYTHON_CFFI_DEPENDENCIES = host-pkgconf libffi
>  PYTHON_CFFI_LICENSE = MIT
>  PYTHON_CFFI_LICENSE_FILES = LICENSE
> +HOST_PYTHON_CFFI_DEPENDENCIES = host-python-pycparser

So, the host variant needs python-pycparser, but the target variantdoes
not?

I would have expect either:
    PYTHON_CFFI_DEPENDENCIES += host-python-pycparser

or:
    PYTHON_CFFI_DEPENDENCIES += python-pycparser

Care to shed some light on this, please?

Regards,
Yann E. MORIN.

>  $(eval $(python-package))
> +$(eval $(host-python-package))
> -- 
> 2.1.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-12-24 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 21:30 [Buildroot] [PATCH 1/5] python-ipaddress: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 2/5] python-pycparser: " Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 3/5] python-cffi: add host variant Yegor Yefremov
2015-12-24 21:46   ` Yann E. MORIN [this message]
2015-12-24 22:12     ` Yegor Yefremov
2015-12-25 19:00       ` Thomas Petazzoni
2015-12-25 19:12         ` Yann E. MORIN
2015-12-25 19:58           ` Yegor Yefremov
2015-12-25 21:44             ` Yann E. MORIN
2015-12-26 22:54               ` Yegor Yefremov
2015-12-31  7:20                 ` Oli Vogt
2015-12-31  8:55                   ` Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 4/5] python-cryptography: new package Yegor Yefremov
2015-12-24 21:30 ` [Buildroot] [PATCH 5/5] python-pyopenssl: " Yegor Yefremov

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=20151224214645.GA3738@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.