On Mon, May 22, 2023 at 02:38:15PM -0500, Andrew Davis wrote: > On 5/22/23 1:38 PM, [email protected] wrote: > >From: Randolph Sapp <[email protected]> > > > >Remove all the legacy arago-sdk build recipies, groups, targets, etc. > >All of this can be replaced by using the Yocto Standard SDK build > >target: > > > > bitbake tisdk-default-image -c populate_sdk > > > >For more info about the SDK build targets see: > >https://docs.yoctoproject.org/sdk-manual/appendix-obtain.html#building-an-sdk-installer > > > >There's probably still more that can be cleaned up, but I'll leave that > >to the more experienced. > > > > Some documentation around this will need cleaned up next cycle. Plus there are > parts of the Processor/Auto/EdgeAI SDK layers that live on top of this layer > that use some of this, they will have to switch to the Yocto Standard SDK now.
1. This cleanup was already in the pipeline, but was planned after the product SDKs (Processor/Auto/EdgeAI) adopttion of Kirkstone baseline with 9.x release. 2. Please stop calling something "the Yocto Standard SDK" - both flows are quite standard. While meta-toolchain was there earlier, it's still a supported and very standard flow. In some cases it is still necessary and preferred. Sure, "populate_sdk" is easier for a single image, as the SDK then matches that image. But if you need an SDK that doesn't depend on an image, or need to cover multiple images, then meta-toolchain is still the way to go. Even OE-Core has meta-toolchain for backward compatibility - it just builds the SDK with the toolchain in it. And meta-qt5 extends that to build its SDK/toolchain with Qt tools. Then AGL defines whole bunch of *-crosssdk recipes that are basically meta-toolchain variants for different purposes with different content. And so on - many layers still use the old flow and it's still very standard. But don't get me wrong - I'm all for simplifying it and removing all the customization cruft that got accumulated in 15 years of Arago! Maybe a bit more surgical and gradual and with a proper description though? :) 3. Have you tested the new SDK and ensured that all use cases are working as expected? Specifically with multiconfig and multiple architectures? -- Denys -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14440): https://lists.yoctoproject.org/g/meta-arago/message/14440 Mute This Topic: https://lists.yoctoproject.org/mt/99071307/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/leave/10763299/21656/89520264/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
