[oe] Where can I get a arm cross toolchain for oe-core?

[Nicolas Dechesne]

On Tue, Apr 15, 2014 at 1:42 PM, Journeyer J. Joh
<oosaprogrammer at gmail.com> wrote:
> I use OE for qualcomm's MDM + AP soc system.
> OE is used on AP side.
>
> The build environment is bitbake based and I felt it like a sandbox system.
> I am sorry I don't know about OE, bitbake very well.. almost I know
> nothing..
>
> I can build the target image. Yes.
> But I wonder how I compile any 3rd party applications for my target.
> I did build one by adding the application source code into the whole image
> source tree.
> This way builds the application as a part of the target image. I can find
> it in /usr/bin with other default applications together.
>
> And I did build another by using a general arm cross toolchain like
> arm-none-linux-gnueabi-gcc.
> Using this toolchain is simple and easy. But there is no gurantee that this
> toolchain has identical libc that is used in the target image. It's not
> only the libc, runtime library, and hardware floating point operation
> configurations are not certain, not guranteed.
>
> I believe there should exist one that 100% syncs with OE bitbake compile
> environment.
> I doubt if I can try to use just OE bitbake environment for those 3rd party
> applications.
>
> How am I supposed to go forward?

you have (at least) 2 options:
 1- create 'native' OE/bitbake recipes for your own
applications/libraries, that way your s/w will be integrated during
the image creation.
 2- use the OE SDK, which produces a toolchain and sysroot compatible
with the image you've built. You can cross compile any application
using this SDK and you're guaranteed that the SDK will match (libc,
...) the content of the target image. For for information about this,
you can look at [1] and [2].

[1] http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html#cross-development-toolchain-generation
[2] http://www.yoctoproject.org/docs/1.5.1/adt-manual/adt-manual.html