[meta-freescale] setting up cross-compiling understanding problems

[Matthias.Heise at atlas-elektronik.com]

Basically I'm trying to understand the whole thing :D : what Yocto/bitbake does and provides and what needs to be provided by me or someone else (e.g. freescale).
In this case I didn't get why the recommended ways for setting up cross-compiling didn't work, but only the optional way.

Would this be correctly put if I say it is a kind of framework which provides meta-data for a lot of sources or packages, (processor)specific ones have to be added, and then it "just" collects and packages the data to an image ?


-----Ursprüngliche Nachricht-----
Von: angolini at gmail.com [mailto:angolini at gmail.com] Im Auftrag von Daiane Angolini
Gesendet: Mittwoch, 19. November 2014 16:15
An: Heise, Matthias
Cc: meta-freescale at yoctoproject.org
Betreff: Re: [meta-freescale] setting up cross-compiling understanding problems

On Mon, Nov 17, 2014 at 12:26 PM,  <Matthias.Heise at atlas-elektronik.com> wrote:
> Hi all,
>
>
>
> you have been very helpful so far with my different noob-problems – 
> thank you very much.
>
> Now I was trying to set up cross-compiling for my wandboard (finally 
> made
> it) and have some difficulties to understand what was happening there 
> and why J
>
> Please be so kind and enlighten me, this is what I tried :
>
>
>
> First of all I copied and renamed the core-image-minimal.bb and added 
> some packages, bitbaked and run it.
>
>
>
> Then for cross-compiling :
>
> http://www.yoctoproject.org/docs/1.7/adt-manual/adt-manual.html#using-
> the-adt-installer
>
> As this was strongly recommended there I first downloaded the 
> adt-installer, extracted it and set up the adt_installer.conf like 
> this (the same also with a bitbaked adt-installer) :
>
> YOCTOADT_TARGETS="arm"
>
> YOCTOADT_QEMU="Y"
>
> YOCTOADT_NFS_UTIL="Y"
>
> YOCTOADT_ROOTFS_arm="minimal sato-sdk"
>
> YOCTOADT_TARGET_SYSROOT_IMAGE_arm="minimal"
>
> YOCTOADT_TARGET_MACHINE_arm="wandboard-quad"
>
> YOCTOADT_TARGET_SYSROOT_LOC_arm="$HOME/test-yocto/$YOCTOADT_TARGET_MACHINE_arm"
>
>
>
> Then I executed the adt_installer script, it finished but had some 
> errors downloading images (probably as I have a “custom” machine, 
> right ?)
>
> I didn’t change the location so that the /opt/poky/1.7 location was used.
> However there were no scripts added to that folder
>
>
>
> After a few tries and half a day I found a tutorial which did this:
>
> bitbake meta-toolchain
>
> sudo ./tmp/deploy/sdk/poky-eglibc-x86_64-arm-toolchain-<version>.sh
>
> source
> /opt/poky/<version>/environment-setup-armv7a-vfp-neon-poky-linux-gnuea
> bi
>
>
>
> then after pointing Eclipse to /opt/poky/1.7 and 
> /opt/poky1.7/sysroots/cortexa9hf……
>
> I was able to compile. (get 3 strange “infos” however : Missing PROG 
> arm-poky… -dlltool, Missing PROG arm-poky… -mt, Missing PROG dlltool)
>
>
>
> What I am wondering about is that this last procedure is headlined as 
> optional in the above mentioned manual, which brings me to the idea 
> that I did something wrong before…
>
> Please comment,

I´m trying to understand what you expect. I didn´t get the question here.

However, it made me think about, maybe, we could include this procedure in our UG. Would you be able to write down the step-by-step you followed?

I can follow it and double check it.

Daiane
>
> Thank you very much,
>
> Best regards,
>
> Mat
>
>
>
>
>
>
>
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>