From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] norm: new package
Date: Tue, 15 Mar 2016 19:14:21 -0300 [thread overview]
Message-ID: <56E8893D.8000505@zacarias.com.ar> (raw)
In-Reply-To: <8737rr8km2.fsf@dell.be.48ers.dk>
On 15/03/16 19:03, Peter Korsgaard wrote:
> The package looks good - But waf is a python script, right? It got me
> wondering if we should use our host-python or if we can rely on the
> build host having all dependencies?
>
> It seems like we have a mix:
>
> package/glmark2/glmark2.mk: $(HOST_DIR)/usr/bin/python2 ./waf configure $(GLMARK2_CONF_OPTS) \
> package/glmark2/glmark2.mk: cd $(@D) && $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/python2 ./waf
> package/glmark2/glmark2.mk: cd $(@D) && $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/python2 ./waf install --destdir=$(TARGET_DIR)
> package/gstreamer1/gst1-imx/gst1-imx.mk: $(HOST_DIR)/usr/bin/python2 ./waf configure $(GST1_IMX_CONF_OPTS)
> package/gstreamer1/gst1-imx/gst1-imx.mk: $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS)
> package/gstreamer1/gst1-imx/gst1-imx.mk: $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) \
> package/jack2/jack2.mk: $(HOST_DIR)/usr/bin/python2 ./waf configure \
> package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS))
> package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) \
> package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(STAGING_DIR) \
> package/libimxvpuapi/libimxvpuapi.mk: $(TARGET_CONFIGURE_OPTS) $(HOST_DIR)/usr/bin/python2 ./waf configure \
> package/libimxvpuapi/libimxvpuapi.mk: $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS)
> package/libimxvpuapi/libimxvpuapi.mk: $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(STAGING_DIR) install
> package/libimxvpuapi/libimxvpuapi.mk: $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) install
> package/samba4/samba4.mk: ./buildtools/bin/waf configure \
>
> E.G. everything else than samba4 uses host-python2.
Hi Peter.
I can't speak for all the rest, but norm uses waf 1.8.11 (I.E. 1.8.x
series) which works fine with python2 or python3, so as long as there's
one host python (at least 2.5) everything should be fine (covered by the
prereqs, and waf is pretty much self-contained).
Regards.
next prev parent reply other threads:[~2016-03-15 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 9:35 [Buildroot] [PATCH 1/2] norm: new package Gustavo Zacarias
2016-03-09 9:35 ` [Buildroot] [PATCH 2/2] zeromq: add norm support Gustavo Zacarias
2016-03-20 22:09 ` Thomas Petazzoni
2016-03-15 22:03 ` [Buildroot] [PATCH 1/2] norm: new package Peter Korsgaard
2016-03-15 22:14 ` Gustavo Zacarias [this message]
2016-03-15 22:19 ` Peter Korsgaard
2016-03-15 22:22 ` Gustavo Zacarias
2016-03-15 22:33 ` Peter Korsgaard
2016-03-15 22:39 ` Gustavo Zacarias
2016-03-20 22:01 ` Thomas Petazzoni
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=56E8893D.8000505@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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