From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sun, 17 Jun 2018 13:47:12 +0200 Subject: [Buildroot] Using a bootlin toolchain with buildroot In-Reply-To: References: <20180406210215.6c276c4f@windsurf.home> <20180407084321.1e68cc90@windsurf.home> <20180615211330.479e44c5@windsurf> Message-ID: <20180617134712.4fbe529e@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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