Skip to contentSkip to conversation

use yocto toolchain as external toolchain

DISCUSSION [email protected] 2 participants 2 messages Mar 18, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

It may sound slightly crazy:) but can I use a toolchain, which was created by Poky as an external toolchain for Poky?

What I am after is something like this:

I create a multiplatfrom v7 compatible Yocto project, which spits out toolchain/rootfs/kernel/various device trees.[1]

Now I need to build for each board a custom u-boot, something like [2][3],...

Obviously [2] and [3] build again the toolchain. Would it be possible to reuse the toolchain built by [1] like an external toolchain to save some build time?

Regards,

Robert

[1] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/multi-v7-ml
[2] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/beagle-bone-black-multi-v7-ml
[3] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/zedboard-multi-v7-ml

#1 lore raw
Quoted 13 lines · On 03/17/2016 12:40 PM, [email protected] wrote:

Hi,

It may sound slightly crazy:) but can I use a toolchain, which was created by Poky as an external toolchain for Poky?

What I am after is something like this:

I create a multiplatfrom v7 compatible Yocto project, which spits out toolchain/rootfs/kernel/various device trees.[1]

Now I need to build for each board a custom u-boot, something like [2][3],...

Obviously [2] and [3] build again the toolchain. Would it be possible to reuse the toolchain built by [1] like an external toolchain to save some build time?

Quoted 8 lines

Regards,

Robert

[1] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/multi-v7-ml
[2] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/beagle-bone-black-multi-v7-ml
[3] https://github.com/RobertBerger/meta-mainline/tree/jethro-training-v4.4.x/zedboard-multi-v7-ml

No need for an external toolchain. Simply point builds [2] & [3] to the sstate-cache from build [1]. This will allow sharing of much of the build, certainly the toolchain, with the subsequent builds. Modify your local.conf to include these lines:
# Reusable state information
SSTATE_MIRRORS ?= "\
file://.* file:///BUILD1/sstate-cache/PATH"
(of course set BUILD1 to the actual path of your build tree)

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------