All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using a bootlin toolchain with buildroot
Date: Sun, 17 Jun 2018 13:47:12 +0200	[thread overview]
Message-ID: <20180617134712.4fbe529e@windsurf> (raw)
In-Reply-To: <CAF_dkJAfn_-H_L3mf8jDnu72D7=UV38sAbRrDQy+nQ=P1XjuYw@mail.gmail.com>

Hello Patrick,

On Sat, 16 Jun 2018 22:28:08 -0400, Patrick Doyle wrote:

> >  4/ Create a tarball of /opt/armv7-eabihf--musl--stable-2018.02-2 and
> >     you're done :-)  
> So, once I do that, I can pull that tarball into my build as if it
> were a bootliin tarball?

Yes.

> And buildroot is smart enough to run the relocate-sdk.sh script
> contained therein?

No, Buildroot is not smart enough to do this, but it's not a problem.
The relocate-sdk.sh is necessary to fixup path in .la files, -config
scripts and stuff like that, which you don't have in a SDK that is just
a pure toolchain. The only thing that really matters is to have
relative RPATH, and that's already done as part of the "make sdk"
target.

Hence, "make sdk" + tarballing output/host already makes a toolchain
that is relocatable, and usable as-is as an external toolchain for
another Buildroot build.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-06-17 11:47 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
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 [this message]
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=20180617134712.4fbe529e@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.