From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Making the Meson integration compatible with per-package folders
Date: Sat, 17 Nov 2018 22:56:46 +0100 [thread overview]
Message-ID: <20181117225646.0874e8f4@gmx.net> (raw)
In-Reply-To: <20181116164859.4c0f4781@windsurf>
Hello Thomas,
On Fri, 16 Nov 2018 16:48:59 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Eric, Peter,
>
> I don't know if you have followed the discussion, but I recently sent a
> new iteration of the per-package folder series [1], which allows to
> support top-level parallel build.
Not in details (and did no test the patches yet)...
>
> Currently the Meson integration in Buildroot doesn't work with this
> per-package folder stuff.
>
> The initial issue is that:
>
> --cross-file=$(HOST_DIR)/etc/meson/cross-compilation.conf
>
> should be:
>
> --cross-file=$$(HOST_DIR)/etc/meson/cross-compilation.conf
>
> But of course, behind that, there's a bigger issue: this
> cross-compilation.conf hardcodes the compiler path, library path, etc.
> However, with per-package folders, we really need to use the compiler
> and libraries from the per-package folder of the current package.
>
> To achieve this, we will need to generate a per-package
> cross-compilation.conf, which is something Peter was already proposing
> in http://patchwork.ozlabs.org/patch/946599/. However, compared to this
> patch, we would need:
>
> (1) Replacing not only the CFLAGS, but also the compiler/library paths.
>
First draft version:
http://patchwork.ozlabs.org/patch/999406/
Maybe $$($$(PKG)_SRCDIR) could be exchanged with $$(HOST_DIR)...
> (2) Producing a final cross-compilation.conf, which can be used by
> people using the toolchain outside of Buildroot.
>
No problem, just keep the original code in package/meson/meson.mk?
Regards,
Peter
> I am sending this e-mail to see if you are willing/available to help on
> this, or if you would like me to take over this work and propose a
> patch series.
>
> Thanks a lot!
>
> Thomas
>
> [1] http://patchwork.ozlabs.org/project/buildroot/list/?series=75909
prev parent reply other threads:[~2018-11-17 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 15:48 [Buildroot] Making the Meson integration compatible with per-package folders Thomas Petazzoni
2018-11-17 21:56 ` Peter Seiderer [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=20181117225646.0874e8f4@gmx.net \
--to=ps.report@gmx.net \
--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