All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/meson: bump version to 0.52.0
Date: Tue, 15 Oct 2019 09:55:08 +0200	[thread overview]
Message-ID: <20191015095508.7a302d24@windsurf.home> (raw)
In-Reply-To: <facb0988-a634-9b7d-5218-ce5179023e5a@mind.be>

On Tue, 15 Oct 2019 09:41:16 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>  meson at least has good support for cross-compilation, including support for
> building tools for the build machine as part of the compilation process.
> However, that currently doesn't work completely because of pkg-config. Indeed,
> the same pkg-config will be used for build and for target.
> 
>  This sys_root option could help with that, because we could set pkgconfig
> directly to $(HOST_DIR)/bin/pkgconf instead of the wrapper (and configure
> pkgconf with $(HOST_DIR) as sysroot by default; the actual sysroot is anyway
> going to be set by the wrapper script).
> 
>  Unfortunately, this is not a complete solution because we still have the
> -static flag that we add in the wrapper script. I don't know if meson has
> support for that.

I haven't thought this through completely, but I believe that
per-package support also requires some flexibility that the wrapper
provides. But again, I haven't thought this through entirely, maybe it
would be doable with the meson sys_root option.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-15  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 13:00 [Buildroot] [PATCH] package/meson: bump version to 0.52.0 Marcin Niestroj
2019-10-14 16:22 ` Adam Duskett
2019-10-14 17:25   ` Yann E. MORIN
2019-10-15  7:41     ` Arnout Vandecappelle
2019-10-15  7:55       ` Thomas Petazzoni [this message]
2019-10-14 16:30 ` James Hilliard

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=20191015095508.7a302d24@windsurf.home \
    --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 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.