From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [FYI] Bootlin external toolchains
Date: Mon, 2 Dec 2019 15:26:01 +0100 [thread overview]
Message-ID: <20191202152601.4ab1c8cd@windsurf> (raw)
In-Reply-To: <CAMw6YJLJae0GcmrDmSY8FZ-uMj+WBybPkBaLQC1wkhooCjoKyQ@mail.gmail.com>
Hello,
+Romain Naour in Cc.
On Mon, 2 Dec 2019 02:47:15 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> Just in case if someone will be interested. I started Buildroot external
> project which provides external toolchains from the Bootlin:
>
> https://toolchains.bootlin.com
>
> The git repo can be found at:
>
> https://github.com/vkochan/buildroot-external-toolchain-bootlin
An effort was started to package the Bootlin external toolchains in
Buildroot itself, some time ago by engineers at Smile. We had some
off-list discussion about this, but I don't think it was ever posted to
the list. The idea back then was to have a script that generates all
the packages, but the design was to have one package for each
toolchain, so it really added a lot of packages.
But I think we should really support these toolchains in Buildroot
proper instead of having an external for them.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-02 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 0:47 [Buildroot] [FYI] Bootlin external toolchains Vadim Kochan
2019-12-02 14:26 ` Thomas Petazzoni [this message]
2019-12-03 9:59 ` Romain Naour
2019-12-03 10:07 ` Vadim Kochan
2019-12-03 11:00 ` Thomas Petazzoni
2019-12-03 11:06 ` Vadim Kochan
2019-12-03 13:57 ` Thomas Petazzoni
2019-12-03 20:52 ` Arnout Vandecappelle
2019-12-03 21:15 ` Arnout Vandecappelle
2019-12-04 21:52 ` Romain Naour
2019-12-09 23:04 ` Arnout Vandecappelle
2019-12-09 15:59 ` 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=20191202152601.4ab1c8cd@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 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.