On 2/3/26 1:30 PM, Denys Dmytriyenko wrote:
On Tue, Feb 03, 2026 at 12:58:52PM -0600, Andrew Davis via
lists.yoctoproject.org wrote:
On 2/3/26 12:07 PM, Ryan Eatmon wrote:
There are still a few remaining files with tisdk in the name after this patch:
find . -name "*tisdk*"
./meta-arago-distro/recipes-tisdk
./meta-arago-distro/recipes-tisdk/tisdk-uenv
./meta-arago-distro/recipes-tisdk/tisdk-uenv/tisdk-uenv.bb
./meta-arago-distro/recipes-tisdk/tisdk-uenv/tisdk-uenv
This recipe I've been wanting to remove for other reasons (DEPLOYDIR
messiness), plan
is either merge this into the U-Boot recipe as it is the consumer of the
deployed
uEnv.txt. Or just move it to meta-tisdk where is actually used for something.
(the version of uEnv.txt in meta-arago is just an empty placeholder file).
./meta-arago-distro/classes/tisdk-sw-manifest.bbclass
./meta-arago-distro/classes/tisdk-bundle.bbclass
./meta-arago-distro/recipes-core/meta/meta-toolchain-arago-tisdk.bb
./meta-arago-distro/recipes-core/meta/meta-toolchain-arago-tisdk.inc
./meta-arago-distro/recipes-core/meta/meta-toolchain-arago-tisdk-server.bb
./meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-toolchain-tisdk-target.bb
./meta-arago-extras/recipes-core/packagegroups/nativesdk-packagegroup-arago-tisdk-host.bb
To be honest I don't know enough about the original intent of the Arago
toolchain
and bundle to feel safe messing with them. I think they should either move into
meta-tisdk, or just be removed depending on discussions on switching to the
Yocto
provided "Standard SDK"[0]. But that would be a project outside of this renaming
What exactly do you mean "switching to the Yocto provided Standard SDK"??
I mean switching to exactly what Yocto provides, nothing custom.
Arago does produce a slightly extended and slightly customized "Standard SDK"
from OE/Yocto perspective. Since that comes from meta-toolchain*, those terms
are sometimes interchangeable...
Moreover, Arago produces 2 Standard SDKs - one for Linux Cortex-A and another
for baremetal Cortex-R. They get named as devkits though, because from TI's
perspective, the "released" SDK is a bundle of devkits, pre-built binaries
and collateral, such as SW manifest in TI own format. That's the point of
tisdk-bundle.bbclass and tisdk-sw-manifest.bbclass
So, everyhting is pretty "Standard" from OE/Yocto perspective. The only
"Custom" part is bundling several separate pieces together into a single
"release" tarball (product teams may create InstallShield executable of it).
So then let's leave that for the product teams if they choose to continue
to do these odd (just my opinion) executable bundle SDK things. We don't
release Core/Arago SDKs that way, so why does this live here in meta-arago?
Besides the 2 bbclasses, the rest of the recipes just slightly extend and
slightly customize existing meta-toolchain* flow and are within the existing
"Standard SDK" framework.
You say "slightly" but the files relating to this make up more than 10% of all
of meta-arago by lines. And they are some dense scripting which I have no good
way of knowing what is still used by downstream product SDKs or not.
Andrew
PR.
Andrew
[0] https://docs.yoctoproject.org/sdk-manual/using.html
Are we planning on addressing the above as well at some point?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17074):
https://lists.yoctoproject.org/g/meta-arago/message/17074
Mute This Topic: https://lists.yoctoproject.org/mt/117553070/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
