From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling Python packages with C extensions with per-package directories
Date: Sat, 30 Nov 2019 22:27:51 +0100 [thread overview]
Message-ID: <20191130222751.510a61f5@windsurf> (raw)
In-Reply-To: <CALFsTFVNJi=CjuySUhgntAYjUvGpLUO78XoRH+bUtOH_1vw9=g@mail.gmail.com>
Hello Asaf,
On Sat, 30 Nov 2019 22:57:47 +0200
Asaf Kahlon <asafka7@gmail.com> wrote:
> Yeah, it looks like some of your additional patches will solve those issues.
>
> Just out of curiosity, do we have any roadmap for merging those patches or any
> "known issues" regarding this feature that have to be resolved?
My plan was to send those additional patches once the core per-package
support would be merged, which happened just a few days ago.
I hope to be able to send those additional patches next week. Note that
they don't fix all problems. For example, it is known that Qt5 is also
broken with per-package support. Andreas had sent a patch series fixing
this, but it was not trivial.
Next week, I will also try to update
https://elinux.org/Buildroot:Top_Level_Parallel_Build to keep track of
the status: what is merged, what is fixed but not merged yet, and what
are the remaining known issues.
I will also send a patch to enable per-package support usage in the
autobuilders. Not for all builds, but for a small fraction of the
builds.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-11-30 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 19:20 [Buildroot] Compiling Python packages with C extensions with per-package directories Asaf Kahlon
2019-11-30 20:07 ` Thomas Petazzoni
2019-11-30 20:57 ` Asaf Kahlon
2019-11-30 21:27 ` Thomas Petazzoni [this message]
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=20191130222751.510a61f5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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