All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] [RFC] Introduce cross-bin directory
Date: Tue, 4 Feb 2020 16:15:46 +0100	[thread overview]
Message-ID: <a18e0834-cec0-5de4-a6c5-48a5f4c94035@mind.be> (raw)
In-Reply-To: <20200204142456.1537358-1-arnout@mind.be>



On 04/02/2020 15:24, Arnout Vandecappelle (Essensium/Mind) wrote:
> This series is the start of a "cross-bin" directory that I've mentioned
> a couple of times already.
> 
> The idea is that host-tools that are meant for cross-building but don't
> encode the cross-target in their name can be put in this directory, and
> we put this directory in front of PATH for cross-compilation. For
> example, the pkg-config wrapper is really a cross-compilation wrapper.
> To be able to support building of host tools with it, we need to add
> environment variables to force host compilation in HOST_CONFIGURE_OPTS.
> By moving the pkg-config wrapper to the cross-bin directory, we can
> avoid that: for cross-compilation (i.e. target packages), the cross-bin
> dir is put in front of PATH, so the pkg-config wrapper for target is
> found. For native compilation (i.e. host packages), the cross-bin dir
> is *not* put in PATH, so the normal pkg-config configuration will be
> used.
> 
> This series does not do that yet for pkg-config itself. It is only done
> for python and python3. The idea is to start with something a little
> bit less far-reaching that pkg-config. Also, the python3 change is
> needed for meson packages that build python modules from C code (e.g.
> recent python-gobject). These need to have _PYTHON_SYSCONFIGDATA_NAME
> set in the environment, but we can't just export that unconditionally
> even for target packages because sometimes (e.g. in libglib2) meson
> builds native python modules as part of the build and those should
> *not* have _PYTHON_SYSCONFIGDATA_NAME set to the target name... The
> python3 wrapper nicely solves this.
> 
> The python2 wrapper is added as well for symmetry, and because it
> allows us to simplify the inner-python-package definitions.
> 
> This series is posted as an RFC, but it can actually be applied as is.
> It is a requirement for many packages that use the newly-added
> gobject-introspection (e.g. gstreamer1, python-gobject).

 Yann noticed that he has posted something similar/related three years ago:

http://lists.busybox.net/pipermail/buildroot/2015-December/147891.html


 Regards,
 Arnout

> 
> Arnout Vandecappelle (5):
>   package/Makefile.in: add HOST_BIN_CROSS
>   package/python3: install wrapper in HOST_BIN_CROSS
>   package/python: install wrapper in HOST_BIN_CROSS
>   package/pkg-python: rely on python wrapper in HOST_BIN_CROSS
>   package/pkg-meson: use TARGET_MAKE_ENV in configure
> 
>  package/Makefile.in               |  5 ++++-
>  package/pkg-meson.mk              |  2 +-
>  package/pkg-python.mk             | 22 +++-------------------
>  package/python/python-wrapper.in  | 10 ++++++++++
>  package/python/python.mk          | 17 ++++++++++++++---
>  package/python3/python-wrapper.in | 24 ++++++++++++++++++++++++
>  package/python3/python3.mk        | 17 ++++++++++++++---
>  7 files changed, 70 insertions(+), 27 deletions(-)
>  create mode 100644 package/python/python-wrapper.in
>  create mode 100644 package/python3/python-wrapper.in
> 

  parent reply	other threads:[~2020-02-04 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 14:24 [Buildroot] [PATCH 0/5] [RFC] Introduce cross-bin directory Arnout Vandecappelle
2020-02-04 14:24 ` [Buildroot] [PATCH 1/5] package/Makefile.in: add HOST_BIN_CROSS Arnout Vandecappelle
2020-02-04 14:24 ` [Buildroot] [PATCH 2/5] package/python3: install wrapper in HOST_BIN_CROSS Arnout Vandecappelle
2020-02-04 14:24 ` [Buildroot] [PATCH 3/5] package/python: " Arnout Vandecappelle
2020-02-04 14:24 ` [Buildroot] [PATCH 4/5] package/pkg-python: rely on python " Arnout Vandecappelle
2020-02-04 14:24 ` [Buildroot] [PATCH 5/5] package/pkg-meson: use TARGET_MAKE_ENV in configure Arnout Vandecappelle
2020-02-04 15:15 ` Arnout Vandecappelle [this message]
2021-05-26 18:45   ` [Buildroot] [PATCH 0/5] [RFC] Introduce cross-bin directory Arnout Vandecappelle

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=a18e0834-cec0-5de4-a6c5-48a5f4c94035@mind.be \
    --to=arnout@mind.be \
    --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.