search

commontorizon / meta-common-torizon

Fork of the TorizonCore OpenEmbedded Distro Layer to create Common TorizonCore
MIT License
9 stars 8 forks source link

RFC: Setup dynamic layers #45

Open drewmoseley opened 2 months ago

drewmoseley commented 2 months ago

Thinking about users of non-Toradex platforms, they may not want all the toradex and freescale layers. I used a combination of BBFILES_DYNAMIC and conditional settings in bblayers.conf to only include the needed layers.

We can't completely remove meta-toradex-bsp-common as some of the bbclasses in there are used in the Torizon metadata. In the future it might be nice to refactor that so we do not need the Toradex BSP layer.

drewmoseley commented 2 months ago

For now this is just for discussion. I'll rebase at some point to get rid of the merge conflicts.

leonheldattoradex commented 1 month ago

This makes a lot of sense to me. Will the manifest stay the same or can we use some other tool to also dynamically download just what's needed?

leograba commented 1 month ago

Looks quite an interesting feature, especially for a setup with many machines from several different vendors.

drewmoseley commented 1 month ago

Yeah, I'm not sure how well repo would handle this. In past projects we had a base XML repo manifest and many others that included it. And I think our current repo does something like this so we can certainly consider reworking the manifest to make it easier to checkout only a subset of the report.

Alternatively, but more of a change, we could consider using Kas as it has even easier workflows to support this. I've played with it a bit and even wrote a python script to help convert a Toradex repo into a kas file but I have not done much testing on it.