From: "Clément Léger via buildroot" <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Etienne Carriere <etienne.carriere@linaro.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/7] package/python-cryptography: enable host package
Date: Mon, 14 Mar 2022 09:47:52 +0100 [thread overview]
Message-ID: <20220314094752.7ea852c1@fixe.home> (raw)
In-Reply-To: <20220312155913.280739e0@windsurf>
Le Sat, 12 Mar 2022 15:59:13 +0100,
Thomas Petazzoni <thomas.petazzoni@bootlin.com> a écrit :
> Hello,
>
> On Fri, 11 Mar 2022 13:36:30 +0100
> Clément Léger <clement.leger@bootlin.com> wrote:
>
> > Enable host package and add needed dependencies.
> >
> > Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
> > Signed-off-by: Clément Léger <clement.leger@bootlin.com>
> > ---
> > package/python-cryptography/python-cryptography.mk | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/package/python-cryptography/python-cryptography.mk b/package/python-cryptography/python-cryptography.mk
> > index a524f729c8..4ff61c7f86 100644
> > --- a/package/python-cryptography/python-cryptography.mk
> > +++ b/package/python-cryptography/python-cryptography.mk
> > @@ -17,6 +17,11 @@ PYTHON_CRYPTOGRAPHY_DEPENDENCIES = \
> > host-python-cffi \
> > host-rustc \
> > openssl
> > +HOST_PYTHON_CRYPTOGRAPHY_DEPENDENCIES = \
> > + host-python-setuptools-rust \
> > + host-python-cffi \
> > + host-rustc \
> > + openssl
>
> Also, I am actually surprised this is enough. Indeed, there are some
> parts in Rust in python-cryptography, so we have quite some extra
> variables for the target packages to handle this:
>
> PYTHON_CRYPTOGRAPHY_ENV = \
> $(PKG_CARGO_ENV) \
> PYO3_CROSS_LIB_DIR="$(STAGING_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)"
> # We need to vendor the Cargo crates at download time
> PYTHON_CRYPTOGRAPHY_DOWNLOAD_POST_PROCESS = cargo
> PYTHON_CRYPTOGRAPHY_DOWNLOAD_DEPENDENCIES = host-rustc
> PYTHON_CRYPTOGRAPHY_DL_ENV = \
> BR_CARGO_MANIFEST_PATH=src/rust/Cargo.toml
>
> For the last 3 variables, I can explain that it possibly worked for you
> because you perhaps already had the python-cryptography tarball in
> DL_DIR downloaded by the host variant of the package. But if you remove
> this tarball, and build just the host variant, I would suspect that it
> will fail to build.
Indeed, I'm using a shared BR2_DL_DIR which might explain why it worked.
>
> However, I can't really explain why your package works without
> HOST_PYTHON_CRYTOGRAPHY_ENV.
>
> Make sure to do a clean build in a Docker container that doesn't have
> Rust installed (there is an official Buildroot Docker image that is
> available for this kind of testing).
Ok, I'll do that.
>
> Thanks!
>
> Thomas
--
Clément Léger,
Embedded Linux and Kernel engineer at Bootlin
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-03-14 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:36 [Buildroot] [PATCH v3 0/7] boot/optee-os: support new optee-os 3.16.0 build dependencies Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 1/7] package/python-cryptography: enable host package Clément Léger via buildroot
2022-03-11 20:43 ` Thomas Petazzoni via buildroot
2022-03-14 8:38 ` Clément Léger via buildroot
2022-03-12 14:59 ` Thomas Petazzoni via buildroot
2022-03-14 8:47 ` Clément Léger via buildroot [this message]
2022-03-11 12:36 ` [Buildroot] [PATCH v3 2/7] boot/optee-os: add support to build with python-cryptography Clément Léger via buildroot
2022-03-11 20:46 ` Thomas Petazzoni via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 3/7] boot/optee-os: bump to version 3.16.0 Clément Léger via buildroot
2022-03-11 20:47 ` Thomas Petazzoni via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 4/7] package/optee-test: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 5/7] package/optee-examples: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 6/7] package/optee-client: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 7/7] package/optee-benchmark: " Clément Léger via buildroot
2022-03-12 20:36 ` [Buildroot] [PATCH v3 0/7] boot/optee-os: support new optee-os 3.16.0 build dependencies Yann E. MORIN
2022-03-14 7:38 ` Clément Léger via buildroot
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=20220314094752.7ea852c1@fixe.home \
--to=buildroot@buildroot.org \
--cc=clement.leger@bootlin.com \
--cc=etienne.carriere@linaro.org \
--cc=thomas.petazzoni@bootlin.com \
/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