External Pre-built Binary Toolchains
summary
Yocto can consume pre-built GCC toolchains (CodeSourcery, Linaro, Arago) by switching to an TC_MODE variable that points to an include which maps GCC/bin/headers, and by using TC_LIBC overrides or providing eGlibc so recipes stop rebuilding libc. Packaging must add compiler/linker/debugger binaries into an SDK (external-*-sdk recipes) rather than only target libs. Canadian-cross support builds 3-stage SDKs for different hosts, and relocatability is solved by embedding LD-linux with $ORIGIN or using shell-stub wrappers when p-shelf tooling is unavailable.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:26Definitions 1/2
- 2:583- Party Toolchains
- 8:28Existing Support
- 11:05Using CodeSourcery
- 14:30Using Linaro
- 17:00Using Own, e.g. Arago
- 20:09Adding Own, e.g. Arago 2/2
- 25:49Issues/Limitations
- 31:25Packaging SDK, Configuration
- 33:03Packaging SDK, Recipe 1/3
- 43:38Toolchain-less SDK 1/2
- 46:49Canadian Cross Overview
- 48:51Canadian Cross in Yocto
- 51:47Self-contained Binaries
- 54:31Relocatability in Denzil
related talks
46mYocto Project Extensible SDK: Simplifying the Workflow for Application Developers
55mBuild Heterogenous System Using Yocto Project
56mCross Platform Enablement for the Yocto Project with Containers
55mOvercoming C++ Embedded Development Tooling Challenges
43mAccelerated Porting of Linux, U-Boot and Yocto for Production Ready Emb...
17mGetting Rid of "It Works on my Machine"
23mtoolchain-agnostic build time improvements
01h 01mLessons Learned from Packaging 10,000+ C++ Projects