From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using a bootlin toolchain with buildroot
Date: Fri, 6 Apr 2018 21:02:15 +0200 [thread overview]
Message-ID: <20180406210215.6c276c4f@windsurf.home> (raw)
In-Reply-To: <CAF_dkJBJAouapTOfS-MEo-cLNHb1birJ74dvChGPgfVG=i6guw@mail.gmail.com>
Hello Patrick,
On Fri, 6 Apr 2018 10:44:24 -0400, Patrick Doyle wrote:
> Are there any tips or tricks to using a bootlin toolchain with
> buildroot(.2018.02)?
>
> I have downloaded armv7-eabihf--musl--stable-2018.02-2.tar.bz2
> unpacket it into /opt.
> I have selected BR2_TOOLCHAIN_EXTERNAL
> I have selected BR2_TOOLCHAIN_EXTERNAL_CUSTOM
> I have selected BR2_TOOLCHAIN_EXTERNAL_PREINSTALLED
> I have specified /opt/armv7-eabihf--musl--stable-2018.02-2/bin for
> BR2_TOOLCHAIN_EXTERNAL_PATH
>
> I could keep listing all of these settings, but I'm not sure how
> useful that would be.
>
> Basically, I'm asking: If I want to use a bootline toolchain, do I
> just go through and choose the options that best seem to match the
> toolchain options, or is there more documentation about doing this
> someplace?
There are two things that will help you :)
First thing, that is currently hidden is that the
toolchains.bootlin.com website has a defconfig fragment for each
toolchain, that is ready to use with Buildroot.
For example, for the toolchain you tried to use, you can simply use the
defconfig at
https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/fragments/armv7-eabihf--musl--stable-2018.02-2.frag.
In general, for any toolchain, you can go to:
https://toolchains.bootlin.com/downloads/releases/toolchains/<ARCH-TUPLE>/fragments/
and find defconfig files for Buildroot.
The second thing that should help is that I'm working on adding the
Bootlin toolchains as "pre-defined" external toolchains in Buildroot,
very much like the Linaro/Sourcery toolchains we already have. I've
started a patch doing that, but it needs more work, especially because
we have so many Bootlin toolchains for various architectures/C
libraries.
Hope this helps,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-06 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 14:44 [Buildroot] Using a bootlin toolchain with buildroot Patrick Doyle
2018-04-06 14:53 ` Jan Kundrát
2018-04-06 19:02 ` Thomas Petazzoni
2018-04-06 19:02 ` Thomas Petazzoni [this message]
2018-04-07 0:50 ` Patrick Doyle
2018-04-07 6:43 ` Thomas Petazzoni
2018-04-08 22:34 ` Patrick Doyle
2018-06-11 19:12 ` Patrick Doyle
2018-06-15 17:05 ` Patrick Doyle
2018-06-15 19:13 ` Thomas Petazzoni
2018-06-17 2:28 ` Patrick Doyle
2018-06-17 11:47 ` Thomas Petazzoni
2018-06-17 19:03 ` Patrick Doyle
2018-06-18 13:22 ` nimaim
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=20180406210215.6c276c4f@windsurf.home \
--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