Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding support for the Rust programming language
Date: Mon, 11 Apr 2016 10:32:11 +0200	[thread overview]
Message-ID: <20160411103211.3d9a1581@free-electrons.com> (raw)
In-Reply-To: <570A77F9.50506@mind.be>

Hello,

On Sun, 10 Apr 2016 17:57:45 +0200, Arnout Vandecappelle wrote:

>   We try to avoid requiring python for a normal build, and use it only for 
> specific scripts at the moment (like graph-depends).

Right, but on the other hand, support/dependencies/dependencies.sh
verifies unconditionally that there is a python interpreter available
on the build machine. So there is not really anything that prevents
from using python stuff during the build. Unless of course this Python
logic starts to use modules not in the Python standard library, of
course.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-11  8:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 20:45 [Buildroot] Adding support for the Rust programming language Eric Le Bihan
2016-04-10 15:57 ` Arnout Vandecappelle
2016-04-11  8:32   ` Thomas Petazzoni [this message]
2016-04-11  9:12     ` Arnout Vandecappelle
2016-04-11  9:13       ` Arnout Vandecappelle
2016-04-11  9:31         ` Thomas Petazzoni
2016-04-11  9:15       ` Baruch Siach
2016-04-11  9:29         ` Arnout Vandecappelle
2016-04-11 11:42           ` Thomas De Schampheleire
2016-04-11 19:03   ` Eric Le Bihan
2016-04-12 20:22     ` 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=20160411103211.3d9a1581@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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