From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: kory.maincent@bootlin.com,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/python-pillow: fix host package build
Date: Sun, 17 Jul 2022 18:26:32 +0200 [thread overview]
Message-ID: <20220717182632.32e8d732@windsurf> (raw)
In-Reply-To: <20220717092020.GF2543@scaer>
On Sun, 17 Jul 2022 11:20:20 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Well, if some package needs host-python-pillow, that's most probably
> because they are going to do some image manipulation at biuld time.
>
> Disabling all image processing options (that require an external
> library, but that's most of them?) is not so nice. It would maybe make
> sense to enable all the image options for which we have host libraries.
>
> Köry, what does your optee-os need from python-pillow? Would this patch
> still work for it?
Before submitting, I did test the optee-os build in the configuration
used by Köry to validate that the minimal host-python-pillow that I
proposed was sufficient, and it was.
That being said, grepping through the optee_os code from ST, I no
longer see where python-pillow is used. I've started a test build to
check this (but I'm pretty sure it was needed at some point, as I
looked into this with Köry).
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-17 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 11:58 [Buildroot] [PATCH] package/python-pillow: fix host package build Thomas Petazzoni via buildroot
2022-07-17 9:20 ` Yann E. MORIN
2022-07-17 16:26 ` Thomas Petazzoni via buildroot [this message]
2022-07-17 16:47 ` Thomas Petazzoni via buildroot
2022-07-17 18:05 ` Yann E. MORIN
2022-08-10 12:43 ` Peter Korsgaard
2022-08-29 9:07 ` Köry Maincent 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=20220717182632.32e8d732@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=asafka7@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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