From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v14 4/5] package/pkg-meson.mk: set Python sysconfigdata
Date: Tue, 22 Oct 2019 22:59:20 +0200 [thread overview]
Message-ID: <20191022225920.7e35e42e@windsurf> (raw)
In-Reply-To: <20191021200438.97453-5-aduskett@gmail.com>
On Mon, 21 Oct 2019 13:04:37 -0700
aduskett at gmail.com wrote:
> + _PYTHON_SYSCONFIGDATA_NAME="$$(if $$(BR2_PACKAGE_PYTHON3),$$(PKG_PYTHON_SYSCONFIGDATA_NAME),_sysconfigdata)" \
Why do we need this conditional on BR2_PACKAGE_PYTHON3 ?
package/pkg-python.mk is using PKG_PYTHON_SYSCONFIGDATA_NAME
unconditionally, regardless of Python 2.x vs. Python 3.x. Could you
explain this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-22 20:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:04 [Buildroot] [PATCH v14 0/5] gobject-introspection: New package aduskett at gmail.com
2019-10-21 20:04 ` [Buildroot] [PATCH v14 1/5] package/libiberty: new package aduskett at gmail.com
2020-01-16 10:33 ` Yegor Yefremov
2019-10-21 20:04 ` [Buildroot] [PATCH v14 2/5] package/prelink-cross: " aduskett at gmail.com
2019-10-21 20:04 ` [Buildroot] [PATCH v14 3/5] package/gdb: depend on libiberty aduskett at gmail.com
2019-10-21 20:04 ` [Buildroot] [PATCH v14 4/5] package/pkg-meson.mk: set Python sysconfigdata aduskett at gmail.com
2019-10-22 20:59 ` Thomas Petazzoni [this message]
2019-10-22 21:58 ` Arnout Vandecappelle
2019-10-22 22:19 ` Arnout Vandecappelle
2019-10-23 19:48 ` Adam Duskett
2019-10-23 20:42 ` Adam Duskett
2019-10-23 20:50 ` Thomas Petazzoni
2019-10-23 21:03 ` Arnout Vandecappelle
2019-10-23 21:27 ` Arnout Vandecappelle
2019-10-24 16:22 ` Adam Duskett
2020-01-27 16:55 ` Giulio Benetti
2019-10-21 20:04 ` [Buildroot] [PATCH v14 5/5] package/gobject-introspection: new package aduskett at gmail.com
2020-02-04 10:53 ` Arnout Vandecappelle
2020-01-26 20:42 ` [Buildroot] [PATCH v14 0/5] gobject-introspection: New package Giulio Benetti
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=20191022225920.7e35e42e@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