All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Adding support for the Rust programming language
Date: Mon, 11 Apr 2016 11:13:45 +0200	[thread overview]
Message-ID: <570B6AC9.2000700@mind.be> (raw)
In-Reply-To: <570B6A67.1000806@mind.be>



On 04/11/16 11:12, Arnout Vandecappelle wrote:
>
>
> On 04/11/16 10:32, Thomas Petazzoni wrote:
>> 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.
>
>   Well, for the fix-rpath stuff we asked Samuel to do in in shell instead of
> python, with the argument that we want to avoid python to be in the critical
> path of a normal build. That said, this would only be for a rust build, not for
> all builds, so it's less critical.
>
>   BTW note that e.g. for waf-based packages, we always use host-python, not
> system python. But that's probably because waf is not python3 compatible.
>
>   So, if python is used, please make sure it runs on any python (with full
> standard library) from python2.4 (RHEL5) to python3.5. That means that using the
> json standard library module is not an option, since it was introduced only in
> python 2.6.

  Unless of course you add a dependency on host-python or host-python3 (make 
sure you select the version that corresponds to the selected target python, to 
avoid unnecessarily building both). Since we can probably consider rust to be a 
big package, adding an addition host-python dependency is acceptable IMHO.

  Regards,
  Arnout

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-04-11  9:13 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
2016-04-11  9:12     ` Arnout Vandecappelle
2016-04-11  9:13       ` Arnout Vandecappelle [this message]
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=570B6AC9.2000700@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.