> > It will just be a matter of imageconfigurator RRECOMMENDing > imageconfigurator-data, and then imageconfigurator-data being > machinearch and doing the per-machine magic however it wants. > > Ross I see. That means the recipe will be split into two recipes. It would be cool, if it can be done with a single recipe. But that would need ability to mark different PACKAGE_ARCHS to different packages of the same recipe.
Splitting the recipe into two has other consequences. 1. The non-data recipe is of no use if the data recipe is not present. 2. The data recipe in the oecore layer will be empty, so it can be dropped from the oecore layer. 3. With that the 2 recipes go in two separate layers which need each other, which is an awkward organization of recipes. Is there any better way to achieve the same without splitting the recipe into 2? Thanks, Nitin -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
