https://github.com/MentorEmbedded/meta-mentor/blob/master/meta-mel/conf/include/drop-toolchain-from-sdk.inc may be of interest to you.
On Wed, Feb 10, 2016 at 9:01 AM Thomas Kaufmann <thomas.kaufm...@duagon.com> wrote: > Hi > > > > I started porting an existing linux system to the latest yocto base. The > hardware TI am 335x based. > > I want to use the external linaro toolchains. Since I use an existing 3.2 > linux kernel as well as an older u-boot, I created a own machine and distro > configuration. I succeed to build and run the target, so far so good. > > > > To incorporate the external toolchains I added > > > > TCMODE = "external-linaro" > > EXTERNAL_TOOLCHAIN = > "/<homedir>/gcc-linaro-5.1-2015.08-x86_64_arm-linux-gnueabihf" > > > > to the local.conf file and > > > > meta-linaro/meta-linaro-toolchain > > > > to the BBLAYERS in bblayers.conf. meta-linaro was cloned using git. > > For my "legacy" packages I adjust "EXTERNAL_TOOLCHAIN" to a gcc-4.9 > version, this seems to work and everything compiles. > > > > Now my next step is to create an SDK distribution. > > When I do do_populate_sdk with bitbake for my image, however the process > seems to compile a new cross compiler for the target as well as various > qemu things and also newer kernel releases. > > > > Is this the preferred way to integrate the linaro toolchain into poky? Can > anybody share their experience? I find various presentations and snippets > about this topic, but nothing is complete. > > How do I create a SDK distribution which does not feature any QEMU (I want > to deploy to target hardware) and uses the existing prebuilt toolchain? > Build host and target sdk host would be x86_64. > > > > Any recommendations are welcome. > > > > regards Thomas Kaufmann > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto