Paul, Thanks for pointing out these areas where it is confusing. Maybe someone on the team can add some comments about the gcc-* recipe stuff. I don't have that understanding but if I am giving more explanation I can update that entry. I believe the term Cross-Development Toolchain" is the same that BitBake builds in the beginning. If not, please someone from the team add some clarification for me and I will update. I will look for the term "SDK" throughout and remedy that. In the beginning of the development of the docs we used the term SDK liberally. Then we decided to weed it out. Seems I need to completely finish that task.
Scott >-----Original Message----- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Paul D. DeRocco >Sent: Tuesday, June 11, 2013 9:07 PM >To: yocto@yoctoproject.org >Subject: [yocto] Need clarification on some terms > >I'm trying a second time to see if I can learn this system. Section 3.4 >contains a short glossary which explains some things and seems to >obscure >others. So perhaps someone can clear up a few simple things. > >"Cross-Development Toolchain: A collection of software development tools >and >utilities that allow you to develop software for targeted >architectures." Is >that different from the toolchain that bitbake builds in the beginning, >and >then uses to build the image? If so, what is it? > >"Following is a list of toolchain recipes..." This is followed by >gcc-cross-initial, gcc-cross-intermediate, gcc-cross. All three of these >things say that the toolchain runs on the host and is used to build >software >for the target. So why are there three of them? What are the differences >among them? It also says that each one is a "native" package. In my >experience, a "native" toolchain has always meant a toolchain that >produces >code for the same machine that the toolchain runs on, while a "cross" >toolchain produces code for a different machine. That's obviously not >what >"native" means in this context, so what does it mean? > >The documentation makes frequent references to "the SDK" without ever >defining it. I know what it means generically, but what is it in the >Yocto >context? And why does the SDK involve yet another set of three >toolchains? >(Oh, and why is one of them called "canadian"?) > >-- > >Ciao, Paul D. DeRocco >Paul mailto:pdero...@ix.netcom.com > > >_______________________________________________ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
