Hi Nicolas Dechesne and Brian Hutchinson, Thank you for the kind reply!
I will try to move to the way you instructed. Thank you! Sincerely Journeyer ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m ---------------------------------------- 2014-04-15 22:06 GMT+09:00 Brian Hutchinson <[email protected]>: > Hi again Journeyer, > > As always, there are more than one way to do things. I generate various > platform toolchains for our application engineers by using bitbake to build > the filesystem image and then the sdk for it as in: > > bitbake core-image-minimal -c populate-sdk (some of the early versions of > OE don't support the populate-sdk command but if you are using a fairly > recent one it should work). > > This will make a shell script that will install the toolchain onto your > host machine. It is located in your build/tmp/deploy directory (I don't > have access to my build machine at the moment so I can't get too specific). > > When you copy over the sdk install script to your host, it will install to > /usr/local/oecore-i686 (name depends on your host) and if you are using > Yocto it will be in /opt/poky/1.x > > If your apps are makefile based, all you have to do is source the > environment setup script (source > environment-setup-armv7a-vfp-neon-oe-linux-gnueabi for example) which will > set up the path and environment variables etc., then you should be able to > build your apps against the same libs etc., that are in the target sysroot > because the sdk you just installed on the host has the same sysroot. > > So in a nut shell, that's how we do it. It keeps the apps guys from having > to learn the bitbake/OE/Angstrom/Arago/Yocto world. > > If you look at the Yocto Documentation, they have this ADT system for > building apps that is pretty well documented. > > If you just google search "-c populate-sdk" I'm sure you will find a bunch > of examples and topics. > > Regards, > > Brian > > > > On Tue, Apr 15, 2014 at 7:42 AM, Journeyer J. Joh > <[email protected]>wrote: > > > Hello, > > > > 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? > > > > Sincerely > > Journeyer > > > > ---------------------------------------- > > Journeyer J. Joh > > o o s a p r o g r a m m e r > > a t > > g m a i l d o t c o m > > ---------------------------------------- > > -- > > _______________________________________________ > > Openembedded-devel mailing list > > [email protected] > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > > > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
